[jira] Created: (MRM-416) Find artifact does not work.
Find artifact does not work. Key: MRM-416 URL: http://jira.codehaus.org/browse/MRM-416 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-2 Reporter: Henry S. Isidro Finding an artifact always shows the 'No results found' message even though the artifact that is being looked for is in the repository. -- 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-371) Unable to add a remote repository
[ http://jira.codehaus.org/browse/MRM-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100128 ] Fabrice BELLINGARD commented on MRM-371: Hi Kerstin, Wendy was talking about the "archiva.xml" file that is in the ".m2" folder located in your user home directory. For instance, if you're running Archiva on Windows, this will be in "C:\Documents and Settings\userId\.m2". A default archiva.xml file is created on the very first start up of Archiva. You can edit it manually and restart Archiva. > Unable to add a remote repository > - > > Key: MRM-371 > URL: http://jira.codehaus.org/browse/MRM-371 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Wendy Smoak >Assignee: Fabrice BELLINGARD > Fix For: 1.0-alpha-2 > > > There is no "Add Repository" link to the right of "Remote Repositories". > Assuming that the 'Add Repository' link at the top (to the right of "Local > Repositories") is intended to also add remote repositories, if I supply a URL > rather than a directory, the new repo does not appear in the list. There is > no error in the log, it just doesn't happen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1957) clause in the activation section has to provide more complex expressions.
[ http://jira.codehaus.org/browse/MNG-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100129 ] Trustin Lee commented on MNG-1957: -- Sounds good to me. > clause in the activation section has to provide more complex > expressions. > - > > Key: MNG-1957 > URL: http://jira.codehaus.org/browse/MNG-1957 > Project: Maven 2 > Issue Type: Improvement > Components: POM >Affects Versions: 2.0, 2.0.1 >Reporter: Trustin Lee > Fix For: 2.0.x > > > For now, provides only one operator '!' which means negation, but > it would be great if i can use '+' and ~ operator: > 1.5+ > 1.1 ~ 1.4 > ~ 1.3 > 1.4 ~ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-612) implement conflict resolution techniques
[ http://jira.codehaus.org/browse/MNG-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100133 ] Mark Hobson commented on MNG-612: - This issue should be targeted for 2.0.x since the new dependency graph API will make this patch obsolete in 2.1. > implement conflict resolution techniques > > > Key: MNG-612 > URL: http://jira.codehaus.org/browse/MNG-612 > Project: Maven 2 > Issue Type: New Feature > Components: Artifacts and Repositories, Design, Patterns & Best > Practices >Reporter: Brett Porter >Assignee: Jason van Zyl >Priority: Critical > Fix For: 2.1.x > > Attachments: MNG-612-2.patch, MNG-612.patch > > Original Estimate: 8 hours > Remaining Estimate: 8 hours > > currently, the collector only: > - selects nearest "suggested" version in a valid range > - latest version from the valid ranges if none suggested > - fails if ranges are over-constrained > This needs to be configurable: > - select newest, even if there is a nearer suggestion > - select oldest, even if there is a nearer suggestion > - fail if all suggestions don't equate or a range results instead of a single > version > - ignore over constrained ranges and fallback to some other algorithm > - select snapshots even if they weren't explicitly specified -- 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-1606) Upload OpenOffice.org Java/Uno 2.2.1
Upload OpenOffice.org Java/Uno 2.2.1 Key: MAVENUPLOAD-1606 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1606 Project: maven-upload-requests Issue Type: Task Reporter: Mirko Nasato OpenOffice.org includes some JARs that can be used in a standalone Java app to connect to a running OpenOffice.org instance. Please find the bundles here: http://www.artofsolving.com/files/m2/juh-2.2.1-bundle.jar http://www.artofsolving.com/files/m2/jurt-2.2.1-bundle.jar http://www.artofsolving.com/files/m2/ridl-2.2.1-bundle.jar http://www.artofsolving.com/files/m2/unoil-2.2.1-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: (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 ] Joakim Erdfelt updated MRM-329: --- Fix Version/s: (was: 1.0-alpha-2) 1.0.x > 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: Joakim Erdfelt >Priority: Blocker > Fix For: 1.0.x > > > 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] Created: (DOXIA-122) [patch] support filename tag
[patch] support filename tag Key: DOXIA-122 URL: http://jira.codehaus.org/browse/DOXIA-122 Project: doxia Issue Type: New Feature Components: Module - Docbook Simple Affects Versions: 1.0-alpha-9 Reporter: Max Berger Priority: Trivial Attachments: filename.patch this patch adds support for the "filename" tag in docbook. -- 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: (MASSEMBLY-222) 2.2-beta-1 regression in assembly descriptor interpolation
2.2-beta-1 regression in assembly descriptor interpolation
--
Key: MASSEMBLY-222
URL: http://jira.codehaus.org/browse/MASSEMBLY-222
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-1
Reporter: Max Bowsher
Priority: Blocker
I have found a significant change in behaviour between 2.1 and 2.2-beta-1,
using the following assembly descriptor:
{code:xml}
dist
tar.gz
no
/foobar-${version}
README.txt
changelog.txt
java.policy
target
/foobar-${version}/jars
foobar-${version}.jar
src/main/scripts
/foobar-${version}/bin
0755
/foobar-${version}/jars
false
{code}
Using 2.1, ${version} interpolates with the version of the project being
assembled.
Using 2.2-beta-1, the ${version} in the interpolates with the
version of each individual dependency, leading to the being
scattered across many directories.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MECLIPSE-283) Can't set ProjectNatures and BuildCommands for a Multi Module Build
Can't set ProjectNatures and BuildCommands for a Multi Module Build --- Key: MECLIPSE-283 URL: http://jira.codehaus.org/browse/MECLIPSE-283 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: multiproject Affects Versions: 2.3 Reporter: Yuri Schimke When running eclipse:eclipse the ProjectNatures and BuildCommands that I set in the parent POM do not get applied to the modules below. I'd like to include the checkstyle and Spring IDE features once at the top level and not have to specify in each individual POM.xml org.apache.maven.plugins maven-eclipse-plugin org.springframework.ide.eclipse.core.springnature com.atlassw.tools.eclipse.checkstyle.CheckstyleNature org.springframework.ide.eclipse.core.springbuilder com.atlassw.tools.eclipse.checkstyle.CheckstyleBuilder -- 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: (MIDEA-97) -DdownloadSources - sources are not in sync with binaries on SNAPSHOT versions
-DdownloadSources - sources are not in sync with binaries on SNAPSHOT versions -- Key: MIDEA-97 URL: http://jira.codehaus.org/browse/MIDEA-97 Project: Maven 2.x IDEA Plugin Issue Type: Bug Affects Versions: 2.0 Environment: win2000 client, proximity repo Reporter: Walter Angerer using the "-DdownloadSources" switch doesn't sync correctly the sources with binaries for SNAPSHOT versions. for reproducing follow these steps: - person A deploys an artifact with version for example 1.0-SNAPSHOT - person B calls "mvn idea:idea -DdownloadSources -U" and the sources and the binaries of the artifact will be correctly downloaded into the local repo - person A again deploys the changed artifact with the same version for example 1.0-SNAPSHOT - person B again calls "mvn idea:idea -DdownloadSources -U" and the binaries will be downloaded correctly but the sources got out of sync meaning the sources from the previous call are not updated -- 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-237) can't release a pom without it's modules
[ http://jira.codehaus.org/browse/MRELEASE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100153 ] Yves Van Steen commented on MRELEASE-237: - If it is possible I would like to see a property to the release plugin -Dblock-reactor that blocks the modules being build/released. mvn -N release:prepare release:perform is the command I use know. and in the configuration of the release plugin ... -N ... This seems to work but is not that clear. Definitly not to maven newbies who just what that one pom released. I've had to roll back some stuff because the -N was forgotten to the command and someone made a mess of things. Defenitily not fun for an administrator but it's my job. You break it, I fix it! The tag will still have all the files and directories in it's path but that I don't mind that much. Maybe you could create an extra property -Dscm-remove-modules property that first of all reacts to the block-reactor property and that sais it removes the module directories from the created tag in the source repository. This would be possible for subversion but not sure for other repository types. So make it scm dependent. Otherwise it was just a configuration in the maven pom like so : ... true true ... If this was in maven, maven would be perfect. To me this is just the last hick up in functionality. > can't release a pom without it's modules > > > Key: MRELEASE-237 > URL: http://jira.codehaus.org/browse/MRELEASE-237 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 >Reporter: Brett Porter > > We have the common pattern of a parent POM which may have modules, but is > released independently from them (plugins, archetypes being a classic > example). This is currently not possible in the release plugin. -- 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: (MENFORCER-10) EnforcerRuleHelper#getComponent() throws exception
EnforcerRuleHelper#getComponent() throws exception -- Key: MENFORCER-10 URL: http://jira.codehaus.org/browse/MENFORCER-10 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Components: Rule API Environment: Windows XP, maven version 2.0.6. Reporter: Scott Myron Assignee: Brian Fox I'm trying to use EnforcerRuleHelper#getComponent() like the example in http://maven.apache.org/shared/maven-enforcer-rule-api/writing-a-custom-rule.html. I'm trying to get the ProjectDependencyAnalyzer component, however, the lookup fails with a ComponentLookupException. I could not find any documentation about how to fix this or if there is any additional configuration I need to specify. -- 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: (MENFORCER-10) EnforcerRuleHelper#getComponent() throws exception
[ http://jira.codehaus.org/browse/MENFORCER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100167 ] Brian Fox commented on MENFORCER-10: I don't believe that's a standard component that can be pulled...hence the lookup exception. Can you just instantiate a singleton in your rule? > EnforcerRuleHelper#getComponent() throws exception > -- > > Key: MENFORCER-10 > URL: http://jira.codehaus.org/browse/MENFORCER-10 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Rule API > Environment: Windows XP, maven version 2.0.6. >Reporter: Scott Myron >Assignee: Brian Fox > > I'm trying to use EnforcerRuleHelper#getComponent() like the example in > http://maven.apache.org/shared/maven-enforcer-rule-api/writing-a-custom-rule.html. > I'm trying to get the ProjectDependencyAnalyzer component, however, the > lookup fails with a ComponentLookupException. I could not find any > documentation about how to fix this or if there is any additional > configuration I need to specify. -- 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: (MENFORCER-10) EnforcerRuleHelper#getComponent() throws exception
[ http://jira.codehaus.org/browse/MENFORCER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100168 ] Scott Myron commented on MENFORCER-10: -- Sure, that's not a problem, I could just create an instance of the DefaultProjectDependencyAnalyzer. Would it be possible to add documentation somewhere that mentions that only standard components can be pulled in using getComponent()? I was under the impression that any component could be found using getComponent(). > EnforcerRuleHelper#getComponent() throws exception > -- > > Key: MENFORCER-10 > URL: http://jira.codehaus.org/browse/MENFORCER-10 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Rule API > Environment: Windows XP, maven version 2.0.6. >Reporter: Scott Myron >Assignee: Brian Fox > > I'm trying to use EnforcerRuleHelper#getComponent() like the example in > http://maven.apache.org/shared/maven-enforcer-rule-api/writing-a-custom-rule.html. > I'm trying to get the ProjectDependencyAnalyzer component, however, the > lookup fails with a ComponentLookupException. I could not find any > documentation about how to fix this or if there is any additional > configuration I need to specify. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2858) Maven isn't looking in all repositories
[ http://jira.codehaus.org/browse/MNG-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100169 ] David Jackman commented on MNG-2858: Thanks for taking another look. I did another test and it appears as though if a repository has one version of the artifact but not the requested version, Maven doesn't look in the other repositories for the correct version. I wanted to do a more controlled test to prove that this was the problem, but I haven't had the time to do it. If you find the time to try this out, please add a comment here. If I somehow find the time to try this (it's on a very long list of things to do, and not doing this item won't get me fired), I'll post a comment. > Maven isn't looking in all repositories > --- > > Key: MNG-2858 > URL: http://jira.codehaus.org/browse/MNG-2858 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.5 >Reporter: David Jackman >Assignee: Brian Fox > > I've created a settings.xml that lists all of our internal repositories (some > Maven 1, some Maven 2). One of these repositories contains the parent POM > for the project I'm trying to build. However, Maven reports that it can't > "locate resource in repository" and lists all of the repositories in > settings.xml. > > Looking at the debug output, it seems like Maven is only looking for the > parent pom in the first of the repositories in this list (the one just after > central). The correct repository is the second one in the list. > > To test this theory, I removed the repository it was having problems with > from settings.xml. Sure enough, Maven found the parent pom just fine. I > also changed the ID of the repository in settings.xml (which changes its > position in the list--must be a HashMap or something) and it found the parent > pom just fine in this situation, 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: (MENFORCER-10) EnforcerRuleHelper#getComponent() throws exception
[ http://jira.codehaus.org/browse/MENFORCER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100173 ] Scott Myron commented on MENFORCER-10: -- It actually turns out that the DefaultProjectDependencyAnalyzer is depending on being started through the container and have its dependencies injected. > EnforcerRuleHelper#getComponent() throws exception > -- > > Key: MENFORCER-10 > URL: http://jira.codehaus.org/browse/MENFORCER-10 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Rule API > Environment: Windows XP, maven version 2.0.6. >Reporter: Scott Myron >Assignee: Brian Fox > > I'm trying to use EnforcerRuleHelper#getComponent() like the example in > http://maven.apache.org/shared/maven-enforcer-rule-api/writing-a-custom-rule.html. > I'm trying to get the ProjectDependencyAnalyzer component, however, the > lookup fails with a ComponentLookupException. I could not find any > documentation about how to fix this or if there is any additional > configuration I need to specify. -- 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: (MENFORCER-10) EnforcerRuleHelper#getComponent() throws exception
[ http://jira.codehaus.org/browse/MENFORCER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100174 ] Brian Fox commented on MENFORCER-10: based on a conversation I had in IRC on this, it looks like you could put that component jar on the classpath of the enforcer and then try to load it. > EnforcerRuleHelper#getComponent() throws exception > -- > > Key: MENFORCER-10 > URL: http://jira.codehaus.org/browse/MENFORCER-10 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Rule API > Environment: Windows XP, maven version 2.0.6. >Reporter: Scott Myron >Assignee: Brian Fox > > I'm trying to use EnforcerRuleHelper#getComponent() like the example in > http://maven.apache.org/shared/maven-enforcer-rule-api/writing-a-custom-rule.html. > I'm trying to get the ProjectDependencyAnalyzer component, however, the > lookup fails with a ComponentLookupException. I could not find any > documentation about how to fix this or if there is any additional > configuration I need to specify. -- 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: (MENFORCER-10) EnforcerRuleHelper#getComponent() throws exception
[ http://jira.codehaus.org/browse/MENFORCER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100175 ] Scott Myron commented on MENFORCER-10: -- This doesn't appear to work. I added the following dependency to the POM of the project the rule should run against and I still get a ComponentLookupException. org.apache.maven.plugins maven-enforcer-plugin . org.apache.maven.shared maven-dependency-analyzer 1.0-alpha-3-SNAPSHOT > EnforcerRuleHelper#getComponent() throws exception > -- > > Key: MENFORCER-10 > URL: http://jira.codehaus.org/browse/MENFORCER-10 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Rule API > Environment: Windows XP, maven version 2.0.6. >Reporter: Scott Myron >Assignee: Brian Fox > > I'm trying to use EnforcerRuleHelper#getComponent() like the example in > http://maven.apache.org/shared/maven-enforcer-rule-api/writing-a-custom-rule.html. > I'm trying to get the ProjectDependencyAnalyzer component, however, the > lookup fails with a ComponentLookupException. I could not find any > documentation about how to fix this or if there is any additional > configuration I need to specify. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-529) Please fix aspectj mavane-metadata.xml
Please fix aspectj mavane-metadata.xml -- Key: MEV-529 URL: http://jira.codehaus.org/browse/MEV-529 Project: Maven Evangelism Issue Type: Task Components: Invalid Metadata Reporter: Richard A. Gill Please update the metadata to reflect the latest (newer) version > 1.5.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: (MRM-417) Unable to view repository contents with IE6
Unable to view repository contents with IE6 --- Key: MRM-417 URL: http://jira.codehaus.org/browse/MRM-417 Project: Archiva Issue Type: Bug Affects Versions: 1.0-alpha-1 Reporter: Wendy Smoak Attempting to visit a url such as http://repo.example.com/archiva/repository/releases/org/apache/struts results in a dialog box: File Download - Security Warning Do you want to save this file? Name: examples Type: Unknown File Type From: repo.mycompany.com The 'file' in question is a directory. you can't see the repo contents. -- 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-1607) Upload Unitils 1.0 rc 3
Upload Unitils 1.0 rc 3 --- Key: MAVENUPLOAD-1607 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1607 Project: maven-upload-requests Issue Type: Task Reporter: Tim Ducheyne -- 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-417) Unable to view repository contents with IE6
[
http://jira.codehaus.org/browse/MRM-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100180
]
Joakim Erdfelt commented on MRM-417:
I suspect that the following bit in the HTTP Response is the culprit.
{noformat}
Content-Type: text/html ;charset="UTF-8"
{noformat}
The extra space before the ';' isn't supposed to be there.
> Unable to view repository contents with IE6
> ---
>
> Key: MRM-417
> URL: http://jira.codehaus.org/browse/MRM-417
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1
>Reporter: Wendy Smoak
>
> Attempting to visit a url such as
> http://repo.example.com/archiva/repository/releases/org/apache/struts results
> in a dialog box:
> File Download - Security Warning
> Do you want to save this file?
> Name: examples
> Type: Unknown File Type
> From: repo.mycompany.com
> The 'file' in question is a directory. you can't see the repo contents.
--
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-417) Unable to view repository contents with IE6
[
http://jira.codehaus.org/browse/MRM-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100179
]
Joakim Erdfelt commented on MRM-417:
Under archiva 1.0-alpha-2 i get the following ...
h4. Get Request
{noformat}
GET /archiva/repository/internal/org/apache/maven/maven-parent/5/ HTTP/1.1
Host: localhost:8080
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20060601
Firefox/2.0.0.4 (Ubuntu-edgy)
Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer:
http://localhost:8080/archiva/repository/internal/org/apache/maven/maven-parent/
Cookie: JSESSIONID=6fm8tmboihcfe;
rbkRememberMe=55ba27e74a224f849eb1ce109bf8173e;
rbkSignon=562b8a4dd0904a0c84060ad472c3e5e0
Authorization: Basic YWRtaW46Ym9iMQ==
{noformat}
h4. Get Response
{noformat}
HTTP/1.x 200 OK
Date: Wed, 20 Jun 2007 19:26:20 GMT
Server: Jetty/5.1.10 (Linux/2.6.17-10-server i386 java/1.5.0_08
DAV: 1
MS-Author-Via: DAV
Content-Type: text/html ;charset="UTF-8"
Etag: "636C5B52201B3432D1CEB6A9B2ECE331-7AFEB923-0112E8E0C238"
Last-Modified: Fri, 01 Jun 2007 20:01:23 GMT
Transfer-Encoding: chunked
{noformat}
> Unable to view repository contents with IE6
> ---
>
> Key: MRM-417
> URL: http://jira.codehaus.org/browse/MRM-417
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1
>Reporter: Wendy Smoak
>
> Attempting to visit a url such as
> http://repo.example.com/archiva/repository/releases/org/apache/struts results
> in a dialog box:
> File Download - Security Warning
> Do you want to save this file?
> Name: examples
> Type: Unknown File Type
> From: repo.mycompany.com
> The 'file' in question is a directory. you can't see the repo contents.
--
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-417) Unable to view repository contents with IE6
[
http://jira.codehaus.org/browse/MRM-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100181
]
Joakim Erdfelt commented on MRM-417:
As seen in Archiva 0.9 ...
h4. Get Request
{noformat}
GET /archiva/repository/internal/org/apache/maven/maven-parent/5/ HTTP/1.1
Host: localhost:8080
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20060601
Firefox/2.0.0.4 (Ubuntu-edgy)
Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer:
http://localhost:8080/archiva/repository/internal/org/apache/maven/maven-parent/
Cookie: JSESSIONID=a1nn6bf1h3k30;
rbkRememberMe=b575e7059b4646929f4f2d67597e4ecc;
rbkSignon=6f1e8ff0467841f6a901a32cc0e007b7
Authorization: Basic YWRtaW46Ym9iMQ==
Pragma: no-cache
Cache-Control: no-cache
{noformat}
h4. Get Response
{noformat}
HTTP/1.x 200 OK
Date: Wed, 20 Jun 2007 19:40:43 GMT
Server: Jetty/5.1.10 (Linux/2.6.17-10-server i386 java/1.5.0_08
DAV: 1
MS-Author-Via: DAV
Content-Type: text/html ;charset="UTF-8"
Etag: "636C5B52201B3432D1CEB6A9B2ECE331-7AFEB923-0112E8E0C238"
Last-Modified: Fri, 01 Jun 2007 20:01:23 GMT
Transfer-Encoding: chunked
{noformat}
> Unable to view repository contents with IE6
> ---
>
> Key: MRM-417
> URL: http://jira.codehaus.org/browse/MRM-417
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1
>Reporter: Wendy Smoak
>
> Attempting to visit a url such as
> http://repo.example.com/archiva/repository/releases/org/apache/struts results
> in a dialog box:
> File Download - Security Warning
> Do you want to save this file?
> Name: examples
> Type: Unknown File Type
> From: repo.mycompany.com
> The 'file' in question is a directory. you can't see the repo contents.
--
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-417) Unable to view repository contents with IE6
[ http://jira.codehaus.org/browse/MRM-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100182 ] Joakim Erdfelt commented on MRM-417: Tested with IE7 under both archiva 1.0 and archiva 0.9. Both versions fail to show the content. > Unable to view repository contents with IE6 > --- > > Key: MRM-417 > URL: http://jira.codehaus.org/browse/MRM-417 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Wendy Smoak > Attachments: screenshot-ie7-on-xp-sp2.jpg > > > Attempting to visit a url such as > http://repo.example.com/archiva/repository/releases/org/apache/struts results > in a dialog box: > File Download - Security Warning > Do you want to save this file? > Name: examples > Type: Unknown File Type > From: repo.mycompany.com > The 'file' in question is a directory. you can't see the repo contents. -- 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-417) Unable to view repository contents with IE6
[ http://jira.codehaus.org/browse/MRM-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joakim Erdfelt updated MRM-417: --- Attachment: screenshot-ie7-on-xp-sp2.jpg > Unable to view repository contents with IE6 > --- > > Key: MRM-417 > URL: http://jira.codehaus.org/browse/MRM-417 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Wendy Smoak > Attachments: screenshot-ie7-on-xp-sp2.jpg > > > Attempting to visit a url such as > http://repo.example.com/archiva/repository/releases/org/apache/struts results > in a dialog box: > File Download - Security Warning > Do you want to save this file? > Name: examples > Type: Unknown File Type > From: repo.mycompany.com > The 'file' in question is a directory. you can't see the repo contents. -- 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-417) Unable to view repository contents with IE6
[ http://jira.codehaus.org/browse/MRM-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100183 ] Wendy Smoak commented on MRM-417: - Comparing the output of wget -S from both versions as suggested by Brett, this line is present in 0.9 and missing in 1.0: Content-Disposition: inline; filename="index.html" (With IE6, 0.9 works fine.) > Unable to view repository contents with IE6 > --- > > Key: MRM-417 > URL: http://jira.codehaus.org/browse/MRM-417 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Wendy Smoak > Attachments: screenshot-ie7-on-xp-sp2.jpg > > > Attempting to visit a url such as > http://repo.example.com/archiva/repository/releases/org/apache/struts results > in a dialog box: > File Download - Security Warning > Do you want to save this file? > Name: examples > Type: Unknown File Type > From: repo.mycompany.com > The 'file' in question is a directory. you can't see the repo contents. -- 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: (MAVENUPLOAD-1604) release ognl 2.7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100184 ] Jesse Kuhnert commented on MAVENUPLOAD-1604: Ok I've deployed to opensymphony via http://maven2.opensymphony.com/ognl/, but I'm not as sure about what the ultimate filesystem structure will look like with the current group rules. It's hard to tell for sure looking at the m2-sync.sh script but if it doesn't work "as is" I would be happy to submit a patch for m2-sync.sh to support multiple groups. > release ognl 2.7 > > > Key: MAVENUPLOAD-1604 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1604 > Project: maven-upload-requests > Issue Type: Task >Reporter: Jesse Kuhnert > > The 2.7 release has been made to a remote repository which can be found here: > http://opencomponentry.com/repository/m2-ibiblio-sync-repo/ognl/ognl/2.7/ . > The main project web site is http://www.ognl.org, but also > http://opensymphony.com/ognl/ since the project was taken over by > opensymphony. > I haven't yet made any new changes to the actual web site (still syncing with > Patrick) so I'm not listed officially on a team list but am visible as the > project lead here: http://jira.opensymphony.com/browse/OGNL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (NMAVEN-83) NUnit compile time assemblies and runtime assemblies can become out of sync
NUnit compile time assemblies and runtime assemblies can become out of sync --- Key: NMAVEN-83 URL: http://jira.codehaus.org/browse/NMAVEN-83 Project: NMaven Issue Type: Improvement Environment: Maven 2.0.6, Windows XP, NMaven 0.14-SNAPSHOT Reporter: Evan Worley Priority: Minor NMaven compiles the test assembly using the NUnit assemblies that are in the GAC or local repository. When the tests are executed nunit-console ran from the command line assuming that is exists on your path. If you are using nunit-console with nunit runtime assemblies that are of a different version than the assemblies used at compile time, your tests will not executed. If you manually run nunit-console to verify the issue you will see a message like the following, >nunit-console IntegrationTest-test.dll NUnit version 2.2.8 Copyright (C) 2002-2003 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov, Charlie Poole. Copyright (C) 2000-2003 Philip Craig. All Rights Reserved. OS Version: Microsoft Windows NT 5.1.2600.0.NET Version: 1.1.4322.2032 The format of the file 'IntegrationTest-test' is invalid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (NMAVEN-83) NUnit compile time assemblies and runtime assemblies can become out of sync
[ http://jira.codehaus.org/browse/NMAVEN-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100188 ] Shane Isbell commented on NMAVEN-83: If you have dual installations of NUnit, you can use the nunitHome configuration parameter within the test plugin configuration to point to the correct version. > NUnit compile time assemblies and runtime assemblies can become out of sync > --- > > Key: NMAVEN-83 > URL: http://jira.codehaus.org/browse/NMAVEN-83 > Project: NMaven > Issue Type: Improvement > Environment: Maven 2.0.6, Windows XP, NMaven 0.14-SNAPSHOT >Reporter: Evan Worley >Priority: Minor > > NMaven compiles the test assembly using the NUnit assemblies that are in the > GAC or local repository. When the tests are executed nunit-console ran from > the command line assuming that is exists on your path. If you are using > nunit-console with nunit runtime assemblies that are of a different version > than the assemblies used at compile time, your tests will not executed. If > you manually run nunit-console to verify the issue you will see a message > like the following, > >nunit-console IntegrationTest-test.dll > NUnit version 2.2.8 > Copyright (C) 2002-2003 James W. Newkirk, Michael C. Two, Alexei A. > Vorontsov, Charlie Poole. > Copyright (C) 2000-2003 Philip Craig. > All Rights Reserved. > OS Version: Microsoft Windows NT 5.1.2600.0.NET Version: 1.1.4322.2032 > The format of the file 'IntegrationTest-test' is invalid. -- 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-417) Unable to view repository contents with IE6
[
http://jira.codehaus.org/browse/MRM-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100189
]
Joakim Erdfelt commented on MRM-417:
Fixed on plexus-webdav.
New SNAPSHOT deployed for plexus-webdav 1.0-alpha-3-SNAPSHOT
Updated archiva/trunk to use new snapshot.
h4. Fixed Get Response
{noformat}
HTTP/1.x 200 OK
Date: Wed, 20 Jun 2007 21:35:26 GMT
Server: Jetty/5.1.10 (Linux/2.6.17-10-server i386 java/1.5.0_08
DAV: 1
MS-Author-Via: DAV
Content-Type: text/html ;charset="UTF-8"
Etag: "636C5B52201B3432D1CEB6A9B2ECE331-7AFEB923-0112E8E0C238"
Last-Modified: Fri, 01 Jun 2007 20:01:23 GMT
Content-Disposition: inline; filename="index.html"
Transfer-Encoding: chunked
{noformat}
> Unable to view repository contents with IE6
> ---
>
> Key: MRM-417
> URL: http://jira.codehaus.org/browse/MRM-417
> Project: Archiva
> Issue Type: Bug
>Affects Versions: 1.0-alpha-1
>Reporter: Wendy Smoak
> Attachments: screenshot-ie7-on-xp-sp2.jpg
>
>
> Attempting to visit a url such as
> http://repo.example.com/archiva/repository/releases/org/apache/struts results
> in a dialog box:
> File Download - Security Warning
> Do you want to save this file?
> Name: examples
> Type: Unknown File Type
> From: repo.mycompany.com
> The 'file' in question is a directory. you can't see the repo contents.
--
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-1608) FontBox/JempBox/PDFBox updates
FontBox/JempBox/PDFBox updates -- Key: MAVENUPLOAD-1608 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1608 Project: maven-upload-requests Issue Type: Task Reporter: Ben Litchfield Please let me know if this is right, this is the first time I have submitted a request for a maven bundle. Additional bundles http://www.pdfbox.org/dist/FontBox-0.1.0-maven.jar http://www.pdfbox.org/dist/JempBox-0.2.0-maven.jar Other Project URLs http://www.jempbox.org/ http://www.fontbox.org/ PDFBox SF Project site http://sourceforge.net/projects/pdfbox shows benlitchfield as project admin Thanks, Ben -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MPA-104) Document Maven's own development process
[ http://jira.codehaus.org/browse/MPA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MNG-1305 to MPA-104: --- Fix Version/s: (was: 2.0.x) Component/s: (was: Design, Patterns & Best Practices) Complexity: (was: Intermediate) Key: MPA-104 (was: MNG-1305) Project: Maven Project Administration (was: Maven 2) > Document Maven's own development process > > > Key: MPA-104 > URL: http://jira.codehaus.org/browse/MPA-104 > Project: Maven Project Administration > Issue Type: Task >Reporter: Jason van Zyl >Assignee: Jason van Zyl > > There is a thread on the dev mailing list: dev process for 2.0.1/2.1 > and I would like to document the outcome of this discussion so we can > subsequently reference 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] Closed: (MPA-92) re-initiation of the development process
[ http://jira.codehaus.org/browse/MPA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MPA-92. --- Resolution: Duplicate Fix Version/s: (was: 2007-q2) > re-initiation of the development process > > > Key: MPA-92 > URL: http://jira.codehaus.org/browse/MPA-92 > Project: Maven Project Administration > Issue Type: Task >Reporter: Brett Porter >Assignee: Brett Porter > > I would like to champion the re-initiation of the development process we > started some time back. I think we need to have a point where we say "from > this time on, only a certain level of quality is acceptable" - and be > prepared to reject changes that don't come with tests, etc. I think it ties > in to what you're doing, so I'll get stuck into that document again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3061) Circular dependencyManagement excludes all classpath dependencies
[
http://jira.codehaus.org/browse/MNG-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-3061:
--
Fix Version/s: 2.0.x
needs to be reviewed for 2.0.x as a regression, or closed if this is 'by design'
> Circular dependencyManagement excludes all classpath dependencies
> -
>
> Key: MNG-3061
> URL: http://jira.codehaus.org/browse/MNG-3061
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
>Affects Versions: 2.0.6
>Reporter: Hugo Palma
>Priority: Critical
> Fix For: 2.0.x
>
>
> It seems that if in the parent pom you have something like:
>
>
>
> org.apache.tapestry
> tapestry-test
> ${project.version}
> test
>
>
>
> when you try to compile the child tapestry-test sub-project it fails because
> it can't find any dependencies. In fact doing "mvn
> dependency:build-classpath" confirms this. As soon as the
> dependencyManagement entry is removed the sub-project compiles just fine.
> This works fine in Maven 2.0.5, it just stopped working in 2.0.6.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3059) Allow pom to override plugin dependencies
[ http://jira.codehaus.org/browse/MNG-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3059: -- Fix Version/s: 2.1-alpha-1 > Allow pom to override plugin dependencies > - > > Key: MNG-3059 > URL: http://jira.codehaus.org/browse/MNG-3059 > Project: Maven 2 > Issue Type: Wish >Affects Versions: 2.1 >Reporter: Eric Redmond >Assignee: Jason van Zyl > Fix For: 2.1-alpha-1 > > Attachments: maven-core.diff > > > Let win out over a plugin's own dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3060) backwards compatible maven command line
[
http://jira.codehaus.org/browse/MNG-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-3060.
-
Resolution: Won't Fix
IMO, this is better to enforce when needed rather than add this layer of
complexity. In general, Maven needs to be backwards compatible (2.0.6 is
hopefully an exception to the rule), so it should be a very minimal edge case.
You might also refer to these scripts as an easy way to switch: MNG-2730
> backwards compatible maven command line
> ---
>
> Key: MNG-3060
> URL: http://jira.codehaus.org/browse/MNG-3060
> Project: Maven 2
> Issue Type: New Feature
> Components: Command Line
>Reporter: Ryan Christianson
>
> I work for a company that is using maven 2.0.4. We are looking at upgrading
> to 2.0.6, but we have many projects that might be broken by the upgrade. This
> means that we need to upgrade all of our old projects, which its expensive.
> I'm wondering if this could be solved by updating the command line tool to
> support multiple installed versions of maven.
> It might work like this:
> - add a "suggested maven version" to pom.xml files (eg.
> 2.0.4
> - update the mvn command line tool to look for the suggested version maven as
> class paths like this:
> - M2_HOME_2_0_4 would be maven 2.0.4, M2_HOME_2_0_6 would be 2.0.6 and so on.
> - if no M2_HOME_{$VERSION} is found, then use M2_HOME
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3062) Allow access to mojoExecution from within plugin.
[ http://jira.codehaus.org/browse/MNG-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3062: -- Fix Version/s: 2.0.x thinking about whether this is a good idea... it is probably not harmful, but I'm not sure if it would also be a best practice not to use it. What is the use case you have? If the executions are structured appropriately, I would think the mojo just runs or not, and the configuration can be used to alter behaviour. > Allow access to mojoExecution from within plugin. > - > > Key: MNG-3062 > URL: http://jira.codehaus.org/browse/MNG-3062 > Project: Maven 2 > Issue Type: Improvement >Affects Versions: 2.0.6 >Reporter: Paul Gier > Fix For: 2.0.x > > Attachments: PluginParameterExpressionEvaluator.patch > > > I would like to be able to access the execution ID from within a plugin. > This could be useful for example to run only certain executions. This could > be done with a small change to the plugin expression evaluator. > I created a patch that would give the plugin access to the current > MojoExecution. -- 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: (SUREFIRE-257) surefire-report reruns tests
[ http://jira.codehaus.org/browse/SUREFIRE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100199 ] Michael Meyer commented on SUREFIRE-257: Any chance that this functionality will be released soon? Maybe in an alpha version of the plugin? > surefire-report reruns tests > > > Key: SUREFIRE-257 > URL: http://jira.codehaus.org/browse/SUREFIRE-257 > Project: Maven Surefire > Issue Type: Bug > Components: report plugin > Environment: maven 2.0 >Reporter: Dirk Sturzebecher > Fix For: 2.4 > > Attachments: MSUREFIREREP-6-patch.txt > > > surefire-report reruns the tests. In my case this is not just annoying, but > leads to a failure, as the VM (probably) is reused and leftovers from the > first tests are (definitly) still present. > I run maven with: clean package 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
