[jira] Updated: (MDEP-115) Dependency sort mojo
[ http://jira.codehaus.org/browse/MDEP-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MDEP-115: --- Fix Version/s: 2.0-alpha-5 > Dependency sort mojo > > > Key: MDEP-115 > URL: http://jira.codehaus.org/browse/MDEP-115 > Project: Maven 2.x Dependency Plugin > Issue Type: New Feature >Affects Versions: 2.0-alpha-4 >Reporter: Paul Gier >Assignee: Brian Fox > Fix For: 2.0-alpha-5 > > Attachments: maven-dependency-plugin-r579844.patch, > MDEP-115-maven-dependency-plugin-r580489-with-test-and-doc.patch > > > I have a few projects that have a large number of dependencies. I would like > to be able to sort them into alphabetical order for easier readability. Also > sometimes the same dependency gets copied and pasted and there is a > duplicate. I created the sort mojo to sort dependencies in alphabetical > order and optionally remove duplicates and group the dependencies by their > scope. -- 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-245) Manifest configuration does not work properly
Manifest configuration does not work properly - Key: MASSEMBLY-245 URL: http://jira.codehaus.org/browse/MASSEMBLY-245 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-1 Environment: XP Reporter: David Hoffer The documentation at http://maven.apache.org/plugins/maven-assembly-plugin/usage.html states..."the Assembly Plugin supports configuration of an element which is identical to that supported by the maven-jar-plugin" However when I add a manifestEntries section just like I have in my maven-jar-plugin configuration, it is ignored by the assembly plugin. The manifest section works but not manifestEntries. I need both sections to work as documented. -- 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: (MNG-3194) logging changes prevent compilation failures from being shown (in the reactor)
[
http://jira.codehaus.org/browse/MNG-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MNG-3194 started by John Casey.
> logging changes prevent compilation failures from being shown (in the reactor)
> --
>
> Key: MNG-3194
> URL: http://jira.codehaus.org/browse/MNG-3194
> Project: Maven 2
> Issue Type: Bug
> Components: Errors, Logging
>Affects Versions: 2.1-alpha-1
>Reporter: Brett Porter
>Assignee: John Casey
>Priority: Blocker
> Fix For: 2.1-alpha-1
>
>
> The Maven build is failing today due to a compilation error, and the output
> looks like:
> {code}
> [java] [INFO] [compiler:testCompile]
> [java] [INFO] Compiling 36 source files to
> /Users/brett/scm/maven/components/maven-project/target/test-classes
> [java] [INFO]
> [java] [INFO]
> [java] [INFO]
>
> [java] [INFO] Reactor Summary:
> [java] [INFO]
>
> [java] [INFO] Apache Maven ..
> SUCCESS [19.247s]
> [java] [INFO] Maven Build Context ...
> SUCCESS [7.503s]
> [java] [INFO] Maven Model ...
> SUCCESS [8.808s]
> [java] [INFO] Maven Local Settings Model
> SUCCESS [1.960s]
> [java] [INFO] Maven Profile Model ...
> SUCCESS [1.031s]
> [java] [INFO] Maven Lifecycle Model .
> SUCCESS [1.659s]
> [java] [INFO] Maven Project Builder .
> FAILED [9.732s]
> [java] [INFO] Maven Plugin API ..
> NOT BUILT
> [java] [INFO] Maven Core
> NOT BUILT
> [java] [INFO] Maven Reporting API ...
> NOT BUILT
> [java] [INFO] Maven Embedder
> NOT BUILT
> [java] [INFO]
>
> [java] [INFO] Error for project: Maven Project Builder (during
> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile)
> [java] [INFO]
>
> [java] [INFO] BUILD ERRORS
> [java] [INFO]
>
> [java] [INFO] Total time: 50 seconds
> [java] [INFO] Finished at: Fri Sep 07 05:13:55 EST 2007
> [java] [INFO] Final Memory: 17M/42M
> [java] [INFO]
>
> {code}
> The compilation errors are missing before the summary.
> I haven't tested this outside 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] Created: (MJAR-85) I want to be able to specify dynamic data for manifestEntries
I want to be able to specify dynamic data for manifestEntries
-
Key: MJAR-85
URL: http://jira.codehaus.org/browse/MJAR-85
Project: Maven 2.x Jar Plugin
Issue Type: Improvement
Affects Versions: 2.1
Environment: XP
Reporter: David Hoffer
In the configuration - archive - manifestEntries section I want to be able to
specify dynamic data for manifestEntries. The dynamic data is the version of
dependent artifacts.
E.x. If I have a dependency on artifactId=abc version=[1.0,2.0)
I want to have a manifest Entry of something like:
${abc.version}
where the end result is that in the MANIFEST file I will have:
myEntry: 1.23
--
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: (MCOMPILER-57) State default source (1.3) and target (1.1) in the documentation
[
http://jira.codehaus.org/browse/MCOMPILER-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCOMPILER-57.
Resolution: Fixed
Patch applied with slight modifications. Thank you!
> State default source (1.3) and target (1.1) in the documentation
>
>
> Key: MCOMPILER-57
> URL: http://jira.codehaus.org/browse/MCOMPILER-57
> Project: Maven 2.x Compiler Plugin
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Gisbert Amm
>Assignee: Dennis Lundberg
>Priority: Trivial
> Attachments: MCOMPILER-57-maven-compiler-plugin.patch
>
>
> The documentation does currently say nothing about the compiler defaults,
> especially source and target version, which is 1.3 and 1.1 (byte code 45.3).
> It would be helpful to add this information to the docs to make the defaults
> obvious.
> Respective mailing list content:
> This has been discussed several times on this list.
> IMO, the default compilation target being 1.1 (or another hard-defined
> version) meets the rule of least surprise. You can argue that you
> don't like 1.1 and you'd prefer 1.3 or even 1.5 but that is another
> discussion.
> In contrast, the rule of most surprise would be "my build changes when
> I change my JDK" or "my build changes when I build things on different
> machines". This is the absolute worst thing you can run into when
> trying to standardize and control your build process.
> If you want to target a specific JDK, then simply add the compiler
> configuration in your poms. If you feel this has not been documented
> sufficiently, then post a RFE in Jira and someone will add some text
> to the proper page(s) on the site.
> Wayne
> On 8/15/07, Gisbert Amm <[EMAIL PROTECTED]> wrote:
> >> Searching for version issues, I had a closer look at the *.class files
> >> generated by Maven2 with the default compiler settings and found that
> >> the first bytes of them are "cafe babe 0003 002D ...", which is byte
> >> code version 45.3 = Java 1.1.
> >>
> >> First I was believing that I had this (target 1.1) configured somewhere
> >> by accident. However, I didn't find any such configuration, therefore I
> >> dug into the plexus-compiler source and found the following in
> >> plexus-site/plexus-components/plexus-compiler/plexus-compilers/plexus-compiler-javac/src/main/java/org/codehaus/plexus/compiler/javac/JavacCompiler.java:
> >>
> >> // TODO: this could be much improved
> >> if ( StringUtils.isEmpty( config.getTargetVersion() ) )
> >> {
> >> // Required, or it defaults to the target of your JDK (eg 1.5)
> >> args.add( "-target" );
> >> args.add( "1.1" );
> >> }
> >> else
> >> {
> >> args.add( "-target" );
> >> args.add( config.getTargetVersion() );
> >> }
> >>
> >> if ( !suppressSource( config ) && StringUtils.isEmpty(
> >> config.getSourceVersion() ) )
> >> {
> >> // If omitted, later JDKs complain about a 1.1 target
> >> args.add( "-source" );
> >> args.add( "1.3" );
> >> }
> >>
> >> Is there any particular reason why target is set to 1.1 here? IMHO, it
> >> breaks the rule of least surprise for I am certainly expecting that the
> >> generated byte code by default has the version of the JDK I'm using the
> >> compiler of. The comment "Required, or it defaults to the target of your
> >> JDK" doesn't give any reason. Does anybody know, why this default is set?
> >>
> >> At least it should be mentioned on
> >> http://maven.apache.org/plugins/maven-compiler-plugin/howto.html to make
> >> it obvious to users. Otherwise people might have problems and need a
> >> long time to find out what's going on (see
> >> http://www.nabble.com/Odd-Compilation-Issue-tf1566644s177.html#a4287495
> >> for an example).
> >>
> >> Regards,
> >> Gisbert
--
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-244) I want to be able to specify the full name of the generated artifact
I want to be able to specify the full name of the generated artifact
Key: MASSEMBLY-244
URL: http://jira.codehaus.org/browse/MASSEMBLY-244
Project: Maven 2.x Assembly Plugin
Issue Type: Improvement
Environment: XP
Reporter: David Hoffer
I want to be able to specify the full name of final artifacts. For example if
using jar-with-dependencies I want to be able to specify the final name as
somename-${version}.xyz. Where ${version} is replaced with the actual version.
I want this to work when using directory-inline & attached goals and likely
others as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIASITETOOLS-5) Generalize DocRenderer interface and directory structure
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIASITETOOLS-5. -- Resolution: Fixed Done in r583279. > Generalize DocRenderer interface and directory structure > > > Key: DOXIASITETOOLS-5 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-5 > Project: Maven Doxia Site Tools > Issue Type: Task > Components: Doc renderer >Affects Versions: 1.0-alpha-9 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > > See http://docs.codehaus.org/display/DOXIA/Proposed+Changes+to+the+DocRenderer -- 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-157) Doxia Book doesn't work with xdoc source files
[ http://jira.codehaus.org/browse/DOXIA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-157. --- Assignee: Lukas Theussl Resolution: Fixed > Doxia Book doesn't work with xdoc source files > -- > > Key: DOXIA-157 > URL: http://jira.codehaus.org/browse/DOXIA-157 > Project: Maven Doxia > Issue Type: Bug > Components: Book >Affects Versions: 1.0-alpha-9 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > Attachments: gioMaven.rar > > > Files with xml extension are parsed by the docbook parser. Doxia book doesn't > recognize the standard Maven site structure to determine the site module. -- 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-155) AbstractXmlParser should recognize CDATA, entities and comments
[ http://jira.codehaus.org/browse/DOXIA-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-155. --- Resolution: Fixed Done in r583267. > AbstractXmlParser should recognize CDATA, entities and comments > --- > > Key: DOXIA-155 > URL: http://jira.codehaus.org/browse/DOXIA-155 > Project: Maven Doxia > Issue Type: Improvement > Components: Core, Module - Docbook Simple, Module - Xdoc, Module - > Xhtml >Affects Versions: 1.0-alpha-9 >Reporter: Lukas Theussl >Assignee: Lukas Theussl > Fix For: 1.0-beta-1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-137) Add comments to sink API
[ http://jira.codehaus.org/browse/DOXIA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-137. --- Assignee: Lukas Theussl Resolution: Fixed Done in r583267. Comments are implemented in Xdoc, Xhtml and Docbook parsers and sinks, and in AptSink. AptParser is still to do. > 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 >Assignee: 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-154) Xdoc parser should recognize
[ http://jira.codehaus.org/browse/DOXIA-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-154. --- Resolution: Fixed Done in r583267. The html specific code needs a separate issue. > Xdoc parser should recognize
[jira] Created: (MAVENUPLOAD-1758) Clickstream 1.0.3
Clickstream 1.0.3 - Key: MAVENUPLOAD-1758 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1758 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina -- 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-1759) xapool 1.4
xapool 1.4 -- Key: MAVENUPLOAD-1759 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1759 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina -- 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: (MCOMPILER-60) Maven Eclipse Compiler has Classpath Resoluri
Maven Eclipse Compiler has Classpath Resoluri - Key: MCOMPILER-60 URL: http://jira.codehaus.org/browse/MCOMPILER-60 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.0.2 Environment: Windows XP; JDK 1.4; Maven 2.0.7 Reporter: Ben Speiser Attachments: MavenEclipseCompilerBug.zip The Maven Eclipse Compiler fails to find classes in rt.jar such as "org.omg.CORBA.Any", even with rt.jar hardcoded as a system dependency. Sample project attached. When switching to the default (javac) compiler, it works 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] Commented: (MRM-512) Unable to convert null repository config to archiva repository.
[ http://jira.codehaus.org/browse/MRM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109419 ] Joakim Erdfelt commented on MRM-512: The changes made with MRM-437 likely fixed this one too. Will verify later > Unable to convert null repository config to archiva repository. > --- > > Key: MRM-512 > URL: http://jira.codehaus.org/browse/MRM-512 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: James William Dumay > Fix For: 1.0-beta-3 > > Attachments: proxy connector removal.log, > update-repository-consumers.log, wrapper.20070924.log > > > Unable to convert null repository config to archiva repository. > I just deleted the default repositories and got a whole bunch of exceptions. > There also seems to be some first start schema exceptions in the logs also. -- 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-518) Changing the internal repository directory has no effect
[
http://jira.codehaus.org/browse/MRM-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109418
]
Joakim Erdfelt commented on MRM-518:
This is a bug in the web interface for 1.0-beta-2.
The dual use of ManagedRepositoryConfiguration and ArchivaRepository caused
this.
Updates were not propogated correctly.
> Changing the internal repository directory has no effect
>
>
> Key: MRM-518
> URL: http://jira.codehaus.org/browse/MRM-518
> Project: Archiva
> Issue Type: Bug
> Components: repository interface
>Affects Versions: 1.0-beta-2
> Environment: solaris 5.10, jdk 6
>Reporter: Mathias Arens
> Fix For: 1.0-beta-3
>
>
> I changed the directory for the internal archiva repository from the default
> setting
> ${ARCHIVA_HOME}/data/repositories/internal
> to a different location. But new dependencies were still downloaded to the
> default/old directory.
> But after I restarted archiva everything 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] Created: (MEV-548) Broken checksums, junit/junit/maven-metadata.xml
Broken checksums, junit/junit/maven-metadata.xml Key: MEV-548 URL: http://jira.codehaus.org/browse/MEV-548 Project: Maven Evangelism Issue Type: Bug Reporter: Max Bowsher Checksums for junit/junit/maven-metadata.xml are broken. Broken checksums in central make it awkward to run with strict checksum mode. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MEV-536) Broken checksums and signature for maven-2.0.7.pom
[ http://jira.codehaus.org/browse/MEV-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Bowsher reopened MEV-536: - md5/sha1 fixed, good. Signature still broken. > Broken checksums and signature for maven-2.0.7.pom > -- > > Key: MEV-536 > URL: http://jira.codehaus.org/browse/MEV-536 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Max Bowsher >Assignee: Henri Yandell > > http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.7/maven-2.0.7.pom > .md5 and .sha1 are broken due to being in incorrect format (generated by BSD > checksum tools?) > .asc is bad signature. -- 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-518) Changing the internal repository directory has no effect
[
http://jira.codehaus.org/browse/MRM-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109411
]
Mathias Arens commented on MRM-518:
---
I changed it over the web interface.
> Changing the internal repository directory has no effect
>
>
> Key: MRM-518
> URL: http://jira.codehaus.org/browse/MRM-518
> Project: Archiva
> Issue Type: Bug
> Components: repository interface
>Affects Versions: 1.0-beta-2
> Environment: solaris 5.10, jdk 6
>Reporter: Mathias Arens
> Fix For: 1.0-beta-3
>
>
> I changed the directory for the internal archiva repository from the default
> setting
> ${ARCHIVA_HOME}/data/repositories/internal
> to a different location. But new dependencies were still downloaded to the
> default/old directory.
> But after I restarted archiva everything 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] Commented: (MDEP-115) Dependency sort mojo
[ http://jira.codehaus.org/browse/MDEP-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109410 ] Paul Gier commented on MDEP-115: Any chance this can go into alpha 5 ? > Dependency sort mojo > > > Key: MDEP-115 > URL: http://jira.codehaus.org/browse/MDEP-115 > Project: Maven 2.x Dependency Plugin > Issue Type: New Feature >Affects Versions: 2.0-alpha-4 >Reporter: Paul Gier >Assignee: Brian Fox > Attachments: maven-dependency-plugin-r579844.patch, > MDEP-115-maven-dependency-plugin-r580489-with-test-and-doc.patch > > > I have a few projects that have a large number of dependencies. I would like > to be able to sort them into alphabetical order for easier readability. Also > sometimes the same dependency gets copied and pasted and there is a > duplicate. I created the sort mojo to sort dependencies in alphabetical > order and optionally remove duplicates and group the dependencies by their > scope. -- 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-252) Error trying to create an EAR project that contains one web module. It doesn't point to the local project, but only tries to find it in the local and remote repositori
[ http://jira.codehaus.org/browse/MECLIPSE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109409 ] Daniel Bourgeois commented on MECLIPSE-252: --- I ran into this issue as well.. On a hunch I took a look at the order of my modules in my parent pom.xml, and noticed the ear was listed before one of my war projects. Normally maven figures out the correct order when doing a build, but for the eclipse plugin, looks like it doesn't resolve the order correctly based on the dependencies. At any rate, I made sure my ear project was the last one in the module order, and that seems to have done the trick. > Error trying to create an EAR project that contains one web module. It > doesn't point to the local project, but only tries to find it in the local > and remote repositories. > -- > > Key: MECLIPSE-252 > URL: http://jira.codehaus.org/browse/MECLIPSE-252 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution >Affects Versions: 2.3 >Reporter: Daniel Alheiros > > I have one structure that defines 3 projects: > project1-jar > project2-war > project3-ear > project2-war is just a WAR that contains the project1-jar as a library > (WEB-INF/lib) > project3-ear is an EAR that contains project2-war as its only web module. > When I run mvn package it works perfectly and creates the EAR containing the > proper WAR file and the application.xml, so it works fine, but when I run mvn > eclipse:eclipse to generate the projects, the ear project is not generated > properly as it tries to find the war in the local and remote repository as > the piece of logging show bellow: > [INFO] Building project3-ear > [INFO]task-segment: [eclipse:eclipse] > [INFO] > > [INFO] Preparing eclipse:eclipse > Downloading: > http://mycompany.central-repository/repo/com/mycompany/project2-war/1.0-SNAPSHOT/project2-war-1.0-SNAPSHOT.war > [WARNING] Unable to get resource > 'mycompanygroupid:project2-war:war:1.0-SNAPSHOT' from repository > mycompany.central-repository (http://mycompany.central-repository/repo) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > Missing: > -- > 1) mycompanygroupid:project2-war:war:1.0-SNAPSHOT > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=mycompanygroupid > -DartifactId=project2-war \ > -Dversion=1.0-SNAPSHOT -Dpackaging=war -Dfile=/path/to/file > Path to dependency: > 1) mycompanygroupid:project3-ear:ear:1.0-SNAPSHOT > 2) mycompanygroupid:project2-war:war:1.0-SNAPSHOT > -- > 1 required artifact is missing. > for artifact: > mycompanygroupid:project3-ear:ear:1.0-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > mycompany.central-repository (http://mycompany.central-repository/repo) > If I follow this instructions and install my WAR file to my local repository, > it then works and makes my EAR project, but I believe it shouldn't be > necessary. -- 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-524) Determine HTTP Cache-Control rules for all repository content.
[ http://jira.codehaus.org/browse/MRM-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-524: - Fix Version/s: (was: 1.0-beta-3) 1.x > Determine HTTP Cache-Control rules for all repository content. > -- > > Key: MRM-524 > URL: http://jira.codehaus.org/browse/MRM-524 > Project: Archiva > Issue Type: Task > Components: repository interface >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt > Fix For: 1.x > > > With the recently added Cache-Control on maven-metadata.xml files from > MRM-503, it becomes apparent that we need to investigate the Cache-Control > rules for other repository content such as ... > * Release Artifacts > * Snapshot Artifacts > * Hashcodes (sha1, md5) -- 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-397) colour inconsistencies on repository admin page
[ http://jira.codehaus.org/browse/MRM-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-397: - Fix Version/s: (was: 1.0-beta-3) 1.x > colour inconsistencies on repository admin page > --- > > Key: MRM-397 > URL: http://jira.codehaus.org/browse/MRM-397 > Project: Archiva > Issue Type: Bug > Components: Users/Security >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter >Assignee: Jesse McConnell >Priority: Trivial > Fix For: 1.x > > > - the grey shading seems to indicate some special property of a given > repository when there are just two (I presume it alternates). I don't think > any alternate shading is needed in boxes of this size > - the background of the archiva logo is not transparent -- 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-504) Find Artifact page needs more onscreen information/instructions
[ http://jira.codehaus.org/browse/MRM-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-504: - Fix Version/s: (was: 1.0-beta-3) 1.x > Find Artifact page needs more onscreen information/instructions > --- > > Key: MRM-504 > URL: http://jira.codehaus.org/browse/MRM-504 > Project: Archiva > Issue Type: Improvement > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Teodoro Cue Jr. > Fix For: 1.x > > > Find Artifact > Search for: > Checksum: > Select the file you would like to locate in the remote repository. The entire > file will not be uploaded to the server. See the progress bar below for > progress of locally creating a checksum that is uploaded to the server after > you hit "Go!". > This page and text and the 'Go' button do not help the user understand what > they can/need to do. > If they should do only one or the other, only one option should be available > at a time. > Recommend changing 'Go' to 'Submit', for consistency w/ Search page. -- 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-402) javadoc jar is listed as just jar in the download box
[ http://jira.codehaus.org/browse/MRM-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-402: - Fix Version/s: (was: 1.0-beta-3) 1.x > javadoc jar is listed as just jar in the download box > - > > Key: MRM-402 > URL: http://jira.codehaus.org/browse/MRM-402 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.x > > Attachments: archiva-bad-downloads-box.jpg > > > go to an artifact that has an attached javadoc jar - you will notice that it > is described as "Jar", not "Javadoc" -- 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-414) Don't queue a request to scan a repository that is currently being scanned
[ http://jira.codehaus.org/browse/MRM-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-414: - Fix Version/s: (was: 1.0-beta-3) 1.x > Don't queue a request to scan a repository that is currently being scanned > -- > > Key: MRM-414 > URL: http://jira.codehaus.org/browse/MRM-414 > Project: Archiva > Issue Type: Improvement > Components: indexing >Affects Versions: 1.0-alpha-1 >Reporter: Wendy Smoak >Priority: Minor > Fix For: 1.x > > > If a repository is currently being scanned when the 'Scan Repository Now' > button is clicked, don't queue another request to scan it. > Example: > INFO | jvm 1| 2007/06/10 21:00:09 | 728900 [SocketListener0-1] INFO > com.opensymphony.xwork.Action:schedulerAction - [ActionMessage] Your request > to have repository [central] be indexed has been queued. > INFO | jvm 1| 2007/06/10 21:00:09 | 728902 [pool-2-thread-1] INFO > org.codehaus.plexus.taskqueue.execution.TaskExecutor:repository-scanning - > Executing task from queue with job name: repository-job:central > INFO | jvm 1| 2007/06/10 21:00:09 | 728928 [pool-2-thread-1] INFO > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default - Walk > Started: [central] file:/opt/central-repository/ > INFO | jvm 1| 2007/06/10 21:01:08 | 788035 [SocketListener0-1] INFO > com.opensymphony.xwork.Action:schedulerAction - [ActionMessage] Your request > to have repository [central] be indexed has been queued. -- 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-196) paginate results
[ http://jira.codehaus.org/browse/MRM-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-196: - Fix Version/s: (was: 1.0-beta-3) 1.x > paginate results > > > Key: MRM-196 > URL: http://jira.codehaus.org/browse/MRM-196 > Project: Archiva > Issue Type: Improvement > Components: web application >Reporter: Brett Porter > Fix For: 1.x > > > reports page, search results, 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] Updated: (MRM-130) improve search results page
[ http://jira.codehaus.org/browse/MRM-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-130: - Fix Version/s: (was: 1.0-beta-3) 1.x > improve search results page > --- > > Key: MRM-130 > URL: http://jira.codehaus.org/browse/MRM-130 > Project: Archiva > Issue Type: Improvement > Components: web application >Reporter: Brett Porter >Assignee: Emmanuel Venisse > Fix For: 1.x > > Original Estimate: 3 hours > Time Spent: 1 hour > Remaining Estimate: 2 hours > > currently, the search results are very plain. We should: > - provide more information about the artifact > - provide more information about the relevance of the result > - provide information about how the search hit occurred (what field) > - paginate the results -- 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-391) Browse repository should display a suitable message when empty
[ http://jira.codehaus.org/browse/MRM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-391: - Fix Version/s: (was: 1.0-beta-3) 1.x > Browse repository should display a suitable message when empty > -- > > Key: MRM-391 > URL: http://jira.codehaus.org/browse/MRM-391 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.x > > > When the configured repositories are empty, the browse page simply lists > nothing. > A suitable message indicating that no repositories are configured, or are not > indexed, or whatever is necessary should be displayed instead. -- 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-157) add a report on artifacts that have external repositories/plugin repositories in them
[ http://jira.codehaus.org/browse/MRM-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-157: - Fix Version/s: (was: 1.0-beta-3) 1.x > add a report on artifacts that have external repositories/plugin repositories > in them > - > > Key: MRM-157 > URL: http://jira.codehaus.org/browse/MRM-157 > Project: Archiva > Issue Type: New Feature > Components: reporting >Reporter: Brett Porter > Fix For: 1.x > > > this may have certain constraints - eg, we report on release repo if it has > any snapshot repos, etc. -- 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-452) repository purge consumer should check that it is running first, and if it consumes an artifact it should prevent other consumers from running
[ http://jira.codehaus.org/browse/MRM-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-452: - Fix Version/s: (was: 1.0-beta-3) 1.x > repository purge consumer should check that it is running first, and if it > consumes an artifact it should prevent other consumers from running > -- > > Key: MRM-452 > URL: http://jira.codehaus.org/browse/MRM-452 > Project: Archiva > Issue Type: Improvement > Components: repository scanning >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter > Fix For: 1.x > > > this is to prevent the index/database getting inconsistent if it scans an > artifact for the first time and decides to delete 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-445) search functions should show a notification message if an initial scan is still in progress
[ http://jira.codehaus.org/browse/MRM-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-445: - Fix Version/s: (was: 1.0-beta-3) 1.x > 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 >Affects Versions: 1.0-beta-2 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.x > > > 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-404) formatting in download box can sometimes be cramped
[ http://jira.codehaus.org/browse/MRM-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-404: - Fix Version/s: (was: 1.0-beta-3) 1.x > formatting in download box can sometimes be cramped > --- > > Key: MRM-404 > URL: http://jira.codehaus.org/browse/MRM-404 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter > Fix For: 1.x > > > go to the "ant:ant:1.6.5" artifact, and look at the download box - the "Jar" > text butts up against the size. > In addition, the size should be displayed in KB instead of bytes (one dec. > pl). -- 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-389) Can't log out or cancel from 'change password' page
[ http://jira.codehaus.org/browse/MRM-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-389: - Fix Version/s: (was: 1.0-beta-3) 1.x > Can't log out or cancel from 'change password' page > --- > > Key: MRM-389 > URL: http://jira.codehaus.org/browse/MRM-389 > Project: Archiva > Issue Type: Bug > Components: Users/Security >Affects Versions: 1.0-alpha-1 >Reporter: Brett Porter >Assignee: Jesse McConnell >Priority: Minor > Fix For: 1.x > > > 1) register a new user > 2) click the validation link from the email > 3) click logout > EXPECTED: normal log out > ACTUAL: stays on the change password page > likewise: > 1) register a new user > 2) click the validation link from the email > 3) click cancel > EXPECTED: return to home page > ACTUAL: stays on the change password page -- 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-518) Changing the internal repository directory has no effect
[
http://jira.codehaus.org/browse/MRM-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109407
]
Brett Porter commented on MRM-518:
--
did you change this in the web interface or the configuration file?
> Changing the internal repository directory has no effect
>
>
> Key: MRM-518
> URL: http://jira.codehaus.org/browse/MRM-518
> Project: Archiva
> Issue Type: Bug
> Components: repository interface
>Affects Versions: 1.0-beta-2
> Environment: solaris 5.10, jdk 6
>Reporter: Mathias Arens
> Fix For: 1.0-beta-3
>
>
> I changed the directory for the internal archiva repository from the default
> setting
> ${ARCHIVA_HOME}/data/repositories/internal
> to a different location. But new dependencies were still downloaded to the
> default/old directory.
> But after I restarted archiva everything 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] Commented: (MRM-512) Unable to convert null repository config to archiva repository.
[ http://jira.codehaus.org/browse/MRM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109408 ] Brett Porter commented on MRM-512: -- is this still an issue? there were significant changes in the space today. > Unable to convert null repository config to archiva repository. > --- > > Key: MRM-512 > URL: http://jira.codehaus.org/browse/MRM-512 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-2 >Reporter: James William Dumay > Fix For: 1.0-beta-3 > > Attachments: proxy connector removal.log, > update-repository-consumers.log, wrapper.20070924.log > > > Unable to convert null repository config to archiva repository. > I just deleted the default repositories and got a whole bunch of exceptions. > There also seems to be some first start schema exceptions in the logs also. -- 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-433) Artifacts file types aren't take in account
[ http://jira.codehaus.org/browse/MRM-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MRM-433. Assignee: Brett Porter Resolution: Duplicate Fix Version/s: (was: 1.0-beta-3) > Artifacts file types aren't take in account > --- > > Key: MRM-433 > URL: http://jira.codehaus.org/browse/MRM-433 > Project: Archiva > Issue Type: Bug > Components: repository interface >Affects Versions: 1.0-alpha-2 > Environment: maven 2.0.7 >Reporter: Mathieu Godlewski >Assignee: Brett Porter > -- 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-534) Test failure in RepositoryContentConsumerUtilTest
[
http://jira.codehaus.org/browse/MRM-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-534:
-
Fix Version/s: 1.0-beta-3
> Test failure in RepositoryContentConsumerUtilTest
> -
>
> Key: MRM-534
> URL: http://jira.codehaus.org/browse/MRM-534
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
> Environment: JDK 1.5.0_11
> Windows XP
> Maven 2.0.7
>Reporter: ajbanck
> Fix For: 1.0-beta-3
>
>
> Building from archiva/trunk, using 'mvn clean build' from the root, JDK
> 1.5.0_11
> 1 test is failing in RepositoryContentConsumerUtilTest:
> ---
> Test set:
> org.apache.maven.archiva.repository.scanner.RepositoryContentConsumerUtilTest
> ---
> Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec <<<
> FAILURE!
> testExecution(org.apache.maven.archiva.repository.scanner.RepositoryContentConsumerUtilTest)
> Time elapsed: 0.031 sec <<< FAILURE!
> junit.framework.AssertionFailedError:
> Expectation failure on verify:
> processFile("path/to/test-file.txt"): expected: 1, actual: 0
> at org.easymock.MockControl.verify(MockControl.java:205)
> at
> org.apache.maven.archiva.repository.scanner.RepositoryContentConsumerUtilTest.testExecution(RepositoryContentConsumerUtilTest.java:140)
--
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-535) metadata-updater is changing lastUpdating timestamp when it shouldn't
[ http://jira.codehaus.org/browse/MRM-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-535: - Fix Version/s: 1.0-beta-3 > metadata-updater is changing lastUpdating timestamp when it shouldn't > - > > Key: MRM-535 > URL: http://jira.codehaus.org/browse/MRM-535 > Project: Archiva > Issue Type: Bug > Components: repository scanning > Environment: JDK 1.5.0_11, Maven 2.0.7 >Reporter: ajbanck >Priority: Minor > Fix For: 1.0-beta-3 > > > This is a bit of a trivial 'bug' and the result is not harmfull, but I think > the metadata-updater should not change data that is valid. > As far as I could find the lastUpdated field is the timestamp on which the > metadata was last updated, so should not be touched in this case. > During scanning, some (~200) maven-metadata.xml files are updated in my > repository . > The metadata being updated is: > > com.informatica.profiling.services > profiling-model-persist > 1.0-SNAPSHOT > > > 20070213.050129 > 79 > > 20070213050130 > > > After update the lastUpdated field is changed to 20070213050129: > 20070213050129 > As far as I could find the lastUpdated field is the timestamp on which the > metadata was last updated, so should not be touched in this case. > Scanlog: > 2007-10-05 14:38:41,043 [pool-2-thread-1] DEBUG > org.apache.maven.archiva.repository.scanner.RepositoryScanner:default - > Sending to consumer: metadata-updater > 2007-10-05 14:38:41,090 [pool-2-thread-1] INFO > org.apache.maven.archiva.consumers.KnownRepositoryContentConsumer:metadata-updater > - Updated metadata: > com/xxx/profiling/services/profiling-model-persist/1.0-SNAPSHOT/maven-metadata.xml > 2007-10-05 14:38:46,356 [pool-2-thread-1] INFO > org.apache.maven.archiva.consumers.KnownRepositoryContentConsumer:metadata-updater > - Updated metadata: > com/xxx/profiling/services/profiling-model-persist/maven-metadata.xml -- 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-532) Unable to specify the location of the index files through the web ui
[ http://jira.codehaus.org/browse/MRM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-532: - Fix Version/s: 1.x > Unable to specify the location of the index files through the web ui > > > Key: MRM-532 > URL: http://jira.codehaus.org/browse/MRM-532 > Project: Archiva > Issue Type: Bug > Components: web application >Affects Versions: 1.0-beta-2 >Reporter: Wendy Smoak >Priority: Minor > Fix For: 1.x > > > There is currently no way to configure the location of the Lucene index files > through the web ui. > Workaround: edit archiva.xml and provide ... > /path/to/index-dir -- 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-1757) JasperReports 2.0.2 upload
JasperReports 2.0.2 upload -- Key: MAVENUPLOAD-1757 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1757 Project: maven-upload-requests Issue Type: Task Reporter: Teodor Danciu http://www.jasperforge.org/maven2/jasperreports-2.0.2-bundle.jar http://sourceforge.net/projects/jasperreports http://sourceforge.net/project/memberlist.php?group_id=36382 Open Source Reporting Engine -- 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-533) Checksum files (sha1/md5) are not kept up to date on maven-metadata.xml files.
[ http://jira.codehaus.org/browse/MRM-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-533: - Priority: Critical (was: Major) Fix Version/s: 1.0-beta-3 cool, one more thing to remove from my list of bugs to file :) > Checksum files (sha1/md5) are not kept up to date on maven-metadata.xml files. > -- > > Key: MRM-533 > URL: http://jira.codehaus.org/browse/MRM-533 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Priority: Critical > Fix For: 1.0-beta-3 > > > When the maven-metadata.xml files are updated, the associated sha1 and md5 > checksums are not updated with 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: (MRM-519) fail to resolve artifactId for libs that contain versionKeyword in artifactId, like "maven-test-plugin"
[ http://jira.codehaus.org/browse/MRM-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109404 ] Brett Porter commented on MRM-519: -- this looks like a case of the current regex (which differs from the one I've used before for the .htaccess file on the central repository) being over-predictive about "test". I think John added this to take care of some edge cases in conversion of the repository - maybe we need to reconsider whether that particular pattern is really needed, or otherwise add another sanity check about the extension and the type in path. > fail to resolve artifactId for libs that contain versionKeyword in > artifactId, like "maven-test-plugin" > --- > > Key: MRM-519 > URL: http://jira.codehaus.org/browse/MRM-519 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-2 >Reporter: nicolas de loof >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > Attachments: RepositoryLayoutUtils.patch > > > Trying to get maven-test-plugin (using maven1) fails in 404. Archiva is > searching for > "\maven\maven\test-plugin-1.8.2\maven-test-plugin-1.8.2.jar" > RepositoryLayoutUtils tries to detect the artifact Id by searching for some > version keyword in the request string. As "test[09]*" is a version keyword, > it resolves to "maven". > The attached path add the feature of checking that all tokens in the version > part - all after artifactId expect the latest (classifier) - are valid > version keywords. -- 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: (DOXIASITETOOLS-5) Generalize DocRenderer interface and directory structure
Generalize DocRenderer interface and directory structure Key: DOXIASITETOOLS-5 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-5 Project: Maven Doxia Site Tools Issue Type: Task Components: Doc renderer Affects Versions: 1.0-alpha-9 Reporter: Lukas Theussl Assignee: Lukas Theussl Fix For: 1.0-beta-1 See http://docs.codehaus.org/display/DOXIA/Proposed+Changes+to+the+DocRenderer -- 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-159) Move DocumentModel from docrenderer into doxia-core
Move DocumentModel from docrenderer into doxia-core Key: DOXIA-159 URL: http://jira.codehaus.org/browse/DOXIA-159 Project: Maven Doxia Issue Type: Task Components: Core Affects Versions: 1.0-alpha-9 Reporter: Lukas Theussl Assignee: Lukas Theussl Fix For: 1.0-beta-1 See http://www.nabble.com/Re%3A-svn-commit%3A-r578786maven-doxia-doxia-trunk-doxia-modules-doxia-module-fo-pom.xml-tf4511463s177.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: (MRM-531) Unable to download snapshots behind proxy with authentication
[ http://jira.codehaus.org/browse/MRM-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109386 ] Mathias Arens commented on MRM-531: --- Oh, I got this error also if I try to download artifacts into the internal repository. But this time I downloaded from an https repository: https://maven-repository.dev.java.net/nonav/repository/ Maybe the proxy settings are not set correctly for https connections as well. INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,233 [SocketListener0-1] WARN org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Resource does not exist: Unable to locate resource in repository INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,234 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [cache-failures] policy with [cached] INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,234 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures - OK to fetch, check-failures detected no issues. INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,234 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [releases] policy with [once] INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,234 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:releases - OK to update releases, local file does not exist. INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,234 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [snapshots] policy with [disabled] INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,234 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:snapshots - OK to update, snapshot policy does not apply for non-snapshot versions. INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,234 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Retrieving org/netbeans/api/org-netbeans-api-visual/RELEASE60-BETA1/org-netbeans-api-visual-RELEASE60-BETA1.jar from EJB3Unit Maven2 Repository if updated INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,644 [SocketListener0-1] WARN org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Resource does not exist: Unable to locate resource in repository INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,644 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [cache-failures] policy with [cached] INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,644 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures - OK to fetch, check-failures detected no issues. INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,644 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [releases] policy with [once] INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,644 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:releases - OK to update releases, local file does not exist. INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,644 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [snapshots] policy with [ignored] INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,644 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:snapshots - OK to update, snapshots policy set to IGNORED. INFO | jvm 1| 2007/10/09 12:28:34 | 2007-10-09 12:28:34,644 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Retrieving org.netbeans.api/jars/org-netbeans-api-visual-RELEASE60-BETA1.jar from Java Dev Maven2 Repository Nonav if updated INFO | jvm 1| 2007/10/09 12:28:35 | 2007-10-09 12:28:35,251 [SocketListener0-1] WARN org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Resource does not exist: Unable to locate resource in repository INFO | jvm 1| 2007/10/09 12:28:35 | 2007-10-09 12:28:35,251 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [cache-failures] policy with [cached] INFO | jvm 1| 2007/10/09 12:28:35 | 2007-10-09 12:28:35,251 [SocketListener0-1] DEBUG org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures - OK to fetch, check-failures detected no issues. INFO | jvm 1| 2007/10/09 12:28:35 | 2007-10-09 12:28:35,251 [SocketListener0-1] DEBUG org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying [releases] policy with [once] INFO | jvm 1| 2007/10/09 12:28:35 | 2007-10-09 12:28:35,251 [Socke
[jira] Created: (NMAVEN-88) ProjectFactory createArtifactFrom() method uses hard coded path ${user.home}/.m2/uac/gac_msil
ProjectFactory createArtifactFrom() method uses hard coded path
${user.home}/.m2/uac/gac_msil
-
Key: NMAVEN-88
URL: http://jira.codehaus.org/browse/NMAVEN-88
Project: NMaven
Issue Type: Bug
Environment: Windows XP, Vista
Reporter: Dan Batten
Firstly let me say that I think this and NMAVEN-87 are somehow associated.
Currently the createArtifactFrom() method of the class
org.apache.maven.dotnet.dao.ProjectFactory is hard coded (maybe this is a bad
use of the term) to use the following path - ${user.home}/.m2/uac/gac_msil.
This causes a problem when the Maven repository is not located in ${user.home},
specifically when compiling projects with references as the reference path
points to the wrong location.
It would be nice if this path was somehow linked to the location of the Maven
repository as it seems some components can handle the repository not existing
in ${user.home}.
My current work-around is simply to compile NMaven with the path to my
repository, so it's not holding me up. I looked into supplying a patch but
unfortunately I'm not intimate enough with the code (I'm working on changing
this).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (NMAVEN-87) ConnectionsRepository is hard coded to use ${user.home}/.m2/uac/rdfRepository
ConnectionsRepository is hard coded to use ${user.home}/.m2/uac/rdfRepository
-
Key: NMAVEN-87
URL: http://jira.codehaus.org/browse/NMAVEN-87
Project: NMaven
Issue Type: Bug
Environment: Windows XP, Vista
Reporter: Dan Batten
Currently the lazyLoad() method of the class
org.apache.maven.dotnet.registry.ConnectionsRepository is hard coded to use the
following path - ${user.home}/.m2/uac/rdfRepository. This causes a problem when
the Maven repository is not located in ${user.home}.
It would be nice if this path was somehow linked to the location of the Maven
repository as it seems some components can handle the repository not existing
in ${user.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
