[jira] Closed: (MJAR-83) addClasspath is not respected for runtime dependencies
[
http://jira.codehaus.org/browse/MJAR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi closed MJAR-83.
Resolution: Fixed
Fix Version/s: 2.2
Applied - thanks.
> addClasspath is not respected for runtime dependencies
> --
>
> Key: MJAR-83
> URL: http://jira.codehaus.org/browse/MJAR-83
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.1, 2.2
>Reporter: William Ferguson
>Assignee: Mauro Talevi
> Fix For: 2.2
>
> Attachments: patch.txt, pom.xml
>
>
> maven-jar-plugin does not resolve dependencies itself, so specifying
> {code}
>
>
>
> true
>
>
>
> {code}
> will add no dependencies for
> {noformat}
> mvn jar:jar
> {noformat}
> And even
> {noformat}
> mvn compiler:compile jar:jar
> {noformat}
> will only add compile time dependencies, not runtime dependencies, presumably
> because the maven-compiler-plugin causes resolution of the compile time
> dependencies.
> See the attached POM.
> There is *no* manifest classpath generated by
> {noformat}
> mvn jar:jar
> {noformat}
> The manifest classpath generated by
> {noformat}
> mvn compiler:compile jar:jar
> {noformat}
> only contains commons-codec which is the compile time dependency.
> There needs to be a way to add runtime dependences to the manifest classpath
> of the jar.
> And preferably not requiring some other plugin to resolve the dependencies
> first.
--
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: (MJAR-30) Allow includes/excludes specification
[ http://jira.codehaus.org/browse/MJAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated MJAR-30: - Description: Allow the specification of includes / excludes to customise jar content. (was: Allow the definition of includes / excludes, so the Jars content can be customized.) Summary: Allow includes/excludes specification (was: Allow inludes/excludes definition) > Allow includes/excludes specification > - > > Key: MJAR-30 > URL: http://jira.codehaus.org/browse/MJAR-30 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Michael Böckling >Assignee: Mauro Talevi > Attachments: fail-patch.txt, maven-jar-plugin-2.2-SNAPSHOT.jar, > MJAR-30-maven-jar-plugin-1.patch, MJAR-30-maven-jar-plugin.patch, > mjar-30.patch > > > Allow the specification of includes / excludes to customise jar content. -- 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: (MJAR-80) excludes is not working for maven-jar-plugin
[ http://jira.codehaus.org/browse/MJAR-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi closed MJAR-80. Resolution: Duplicate Fix Version/s: 2.2 Duplicates MJAR-30. > excludes is not working for maven-jar-plugin > > > Key: MJAR-80 > URL: http://jira.codehaus.org/browse/MJAR-80 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: unix >Reporter: Zhu Fang >Priority: Critical > Fix For: 2.2 > > > The "excludes" is not working for me in maven2 maven-jar-plugin. > anyone has any suggestion/example how to make it work? > Is this a bug of maven-jar-plugin? if it is, how to find a workaround? > I can not exclude it from the source, but got to exclude from the class file. > Thanks a lot! -- 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: (MJAR-30) Allow includes/excludes specification
[ http://jira.codehaus.org/browse/MJAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated MJAR-30: - Attachment: (was: MJAR-30-maven-jar-plugin.patch) > Allow includes/excludes specification > - > > Key: MJAR-30 > URL: http://jira.codehaus.org/browse/MJAR-30 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Michael Böckling >Assignee: Mauro Talevi > Attachments: fail-patch.txt, maven-jar-plugin-2.2-SNAPSHOT.jar, > MJAR-30-maven-jar-plugin-1.patch > > > Allow the specification of includes / excludes to customise jar content. -- 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: (MJAR-30) Allow includes/excludes specification
[ http://jira.codehaus.org/browse/MJAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated MJAR-30: - Attachment: (was: mjar-30.patch) > Allow includes/excludes specification > - > > Key: MJAR-30 > URL: http://jira.codehaus.org/browse/MJAR-30 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Michael Böckling >Assignee: Mauro Talevi > Attachments: fail-patch.txt, maven-jar-plugin-2.2-SNAPSHOT.jar, > MJAR-30-maven-jar-plugin-1.patch > > > Allow the specification of includes / excludes to customise jar content. -- 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: (MJAR-30) Allow includes/excludes specification
[ http://jira.codehaus.org/browse/MJAR-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109841 ] Mauro Talevi commented on MJAR-30: -- Johan, MJAR-30-maven-jar-plugin-1.patch has been applied. Thanks for a very well tested patch! I'm keeping issue open for two reasons: 1. ITs can be improved for readability. I'd like to rename them to reflect what test case they are testing rather than having them by issue number (BTW why the duplication of MJAR-30 and MJAR-80 tests?). 2. Oddly, while tests upon install are successful, tests upon deploy fail. More investigation is needed, although I suspect some setup-related problem. In the meantime, I've deployed a snapshot to snapshot repo (http://people.apache.org/repo/m2-snapshot-repository) > Allow includes/excludes specification > - > > Key: MJAR-30 > URL: http://jira.codehaus.org/browse/MJAR-30 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Reporter: Michael Böckling >Assignee: Mauro Talevi > Attachments: fail-patch.txt, maven-jar-plugin-2.2-SNAPSHOT.jar, > MJAR-30-maven-jar-plugin-1.patch > > > Allow the specification of includes / excludes to customise jar content. -- 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: (MRESOURCES-47) POM properties cannot be accessed within a filter file
[
http://jira.codehaus.org/browse/MRESOURCES-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi closed MRESOURCES-47.
--
Resolution: Fixed
William, applied patch and added IT test.
I've made all static methods public in PropertyUtils but refactored one to use
the other as you proposed.
There may be an argument for refactoring property access as a whole, but that
should be treated as a separate issue (refactor rather than enhancement), so
I'm closing this issue.
Snapshot has been deployed to
http://people.apache.org/repo/m2-snapshot-repository for test.
> POM properties cannot be accessed within a filter file
> --
>
> Key: MRESOURCES-47
> URL: http://jira.codehaus.org/browse/MRESOURCES-47
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: William Ferguson
>Assignee: Mauro Talevi
> Fix For: 2.3
>
> Attachments: MRESOURCES-47-maven-resources-plugin.patch, project.zip
>
>
> Before applying a filter, the maven-resources-plugin evaluates
> 1) POM structural elements such as ${project.version}
> 2) System properties such as ${my.system.property}
> that are referred to within *filter* files.
> However, it does *not* evaluate any POM (or profile) property such as
> ${my.pom.property} at the same time.
> Consequently it is not possible to define filter tokens that use POM
> properties.
> Without this patch we would either need to have many more POM properties or
> would have lots of fine grained and typically non-intuitive tokens
> distributed amongst our resources.
> IMHO this patch will bring the resolution mechanism for filter files in line
> with property resolution mechanism in general.
> I have attached a zipped project containing :
> SomeResource.txt
> my.filter
> Look at SomeResource.txt after being processed with filtering. Note the
> unresolved tokens for ${projectProperty} and ${profileProperty} for the
> "filter resolution" cases. Ie the POM property values of the filter tokens
> were never evaluated.
--
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-539) Make security level of repository more obvious on admin/repositories screen.
[ http://jira.codehaus.org/browse/MRM-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109845 ] Brett Porter commented on MRM-539: -- that was a pretty off-the-cuff observation on my part - I was emphasising it needed it's own jira, 'tis all :) Friendly assignment for guest only might be a suitable idea - needs more thought. > Make security level of repository more obvious on admin/repositories screen. > > > Key: MRM-539 > URL: http://jira.codehaus.org/browse/MRM-539 > Project: Archiva > Issue Type: Improvement > Components: Users/Security >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Priority: Minor > > Make the repositories screen show the security level of the repository. > Make the repository configuration process simplify the role assignments. > Pre-configure the default-archiva.xml repositories for public, read-only > security level. > Technical Details: > 1) Add a field ManagedRepositoryConfiguration.security (with possible value: > public-read-only, public-read-write, access-controlled) > 2) Configure the default-archiva.xml with that field set true. > 3) Configure the UI for repositories to show/set/change that value. > 4) Integrate the guest user role assignments to that field. -- 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-539) Make security level of repository more obvious on admin/repositories screen.
[ http://jira.codehaus.org/browse/MRM-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-539: - Fix Version/s: 1.x > Make security level of repository more obvious on admin/repositories screen. > > > Key: MRM-539 > URL: http://jira.codehaus.org/browse/MRM-539 > Project: Archiva > Issue Type: Improvement > Components: Users/Security >Affects Versions: 1.0-beta-2 >Reporter: Joakim Erdfelt >Priority: Minor > Fix For: 1.x > > > Make the repositories screen show the security level of the repository. > Make the repository configuration process simplify the role assignments. > Pre-configure the default-archiva.xml repositories for public, read-only > security level. > Technical Details: > 1) Add a field ManagedRepositoryConfiguration.security (with possible value: > public-read-only, public-read-write, access-controlled) > 2) Configure the default-archiva.xml with that field set true. > 3) Configure the UI for repositories to show/set/change that value. > 4) Integrate the guest user role assignments to that field. -- 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-536) JVM Bug Triggered in archiva-metadata-reports
[
http://jira.codehaus.org/browse/MRM-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109846
]
Brett Porter commented on MRM-536:
--
can we really aim to fix this?
Is it 100% reproducible? If so, does upgrading to JDK 5.0 update 13 help?
I don't see it here.
> JVM Bug Triggered in archiva-metadata-reports
> -
>
> Key: MRM-536
> URL: http://jira.codehaus.org/browse/MRM-536
> Project: Archiva
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0-beta-3
>Reporter: Joakim Erdfelt
> Attachments: hs_err_pid30832.log
>
>
> {noformat}
> ---
> T E S T S
> ---
> There are no tests to run.
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO] [jar:jar]
> [INFO] Building jar:
> /home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/
> archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
> [INFO] [install:install]
> [INFO] Installing
> /home/joakim/code/archiva/trunk/archiva-reporting/archiva-metadata-reports/target/
> archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar to
> /home/joakim/.m2/repository-archiva/org/apache/maven/archiva/archiva-metadata-re
> ports/1.0-beta-3-SNAPSHOT/archiva-metadata-reports-1.0-beta-3-SNAPSHOT.jar
> [INFO]
>
> [INFO] Building Archiva Reporting :: Project Reports
> [INFO]task-segment: [clean, install]
> [INFO]
>
> [INFO] [clean:clean]
> [INFO] Deleting directory
> /home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target
> [INFO] Deleting directory
> /home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/classes
> [INFO] Deleting directory
> /home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/test-classes
> [INFO] Deleting directory
> /home/joakim/code/archiva/trunk/archiva-reporting/archiva-project-reports/target/site
> [INFO] [plexus:descriptor {execution: generate}]
> [INFO] [remote-resources:process {execution: default}]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> #
> # An unexpected error has been detected by HotSpot Virtual Machine:
> #
> # SIGSEGV (0xb) at pc=0xb79a4afd, pid=30832, tid=3085063872
> #
> # Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode, sharing)
> # Problematic frame:
> # V [libjvm.so+0x324afd]
> #
> # An error report file with more information is saved as hs_err_pid30832.log
> #
> # If you would like to submit a bug report, please visit:
> # http://java.sun.com/webapps/bugreport/crash.jsp
> #
> Aborted (core dumped)
> {noformat}
--
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: (ARCHETYPE-62) Allow package.html files to be included in an archetype
[ http://jira.codehaus.org/browse/ARCHETYPE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109848 ] Heinrich Nirschl commented on ARCHETYPE-62: --- With the patch for MJAR-30 there is now a workaround: Configure the jar plugin with a dummy exclude to override the default some-file-that-does-not-exist > Allow package.html files to be included in an archetype > --- > > Key: ARCHETYPE-62 > URL: http://jira.codehaus.org/browse/ARCHETYPE-62 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 1.0-alpha-4 >Reporter: Martin Ahrer > > A Java source folder may contain non Java resources such as JavaDoc > package.html etc. > > src/main/java/App.java > src/main/java/package.html > > > src/test/java/AppTest.java > src/main/java/package.html > > Currently when specifying non Java resources they don't get distributed in > the packaged archetype jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1767) Upload junit toolkit maven plugin 0.6.1
Upload junit toolkit maven plugin 0.6.1 --- Key: MAVENUPLOAD-1767 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1767 Project: maven-upload-requests Issue Type: Task Reporter: Rupert Smith JUnit Toolkit enhances JUnit with performance testing, asymptotic behaviour analysis, and concurrency testing. -- 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-1768) Upload junit toolkit 0.6.1
Upload junit toolkit 0.6.1 -- Key: MAVENUPLOAD-1768 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1768 Project: maven-upload-requests Issue Type: Task Reporter: Rupert Smith JUnit Toolkit enhances JUnit with performance testing, asymptotic behaviour analysis, and concurrency testing. -- 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: (MRM-459) prune the distributed dependencies
[ http://jira.codehaus.org/browse/MRM-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MRM-459: -- jstl-api can't be removed, not all appservers provide it (see Wendy's message to dev list, <[EMAIL PROTECTED]>) > prune the distributed dependencies > -- > > Key: MRM-459 > URL: http://jira.codehaus.org/browse/MRM-459 > Project: Archiva > Issue Type: Improvement > Components: web application >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > a large number of unneeded dependencies are distributed with Archiva (or if > they are needed, we might want to review why). > For example: ant-optional (probably for jsp compiler), commons-logging impl + > slf4j + log4j, xerces, jtidy, jdom, dom4j, commons-jxpath, jaxen, jta (we > have geronimo-jat already), classworlds (we have plexus-classworlds already), > backport (we require JDK 5, no need for this). > I'm also uncertain if all the maven libraries are still needed. -- 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-459) prune the distributed dependencies
[ http://jira.codehaus.org/browse/MRM-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109856 ] Brett Porter commented on MRM-459: -- we should also be able to remove more: - was xml-apis removed as well as xerces? - only velocity is needed, not velocity-dep (as long as we have all the deps included in velocity-dep, which I think we do) - we should be smarter about logging. Don't need clogging and clogging-api, don't need slf4j simple. I think the rest are right since we need both apis :( - do we really need jtidy? - can we do anything about the JCA lib? is there one from Geronimo? - where are the Maven libs still used? > prune the distributed dependencies > -- > > Key: MRM-459 > URL: http://jira.codehaus.org/browse/MRM-459 > Project: Archiva > Issue Type: Improvement > Components: web application >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > a large number of unneeded dependencies are distributed with Archiva (or if > they are needed, we might want to review why). > For example: ant-optional (probably for jsp compiler), commons-logging impl + > slf4j + log4j, xerces, jtidy, jdom, dom4j, commons-jxpath, jaxen, jta (we > have geronimo-jat already), classworlds (we have plexus-classworlds already), > backport (we require JDK 5, no need for this). > I'm also uncertain if all the maven libraries are still needed. -- 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-531) Unable to download snapshots behind proxy with authentication
[ http://jira.codehaus.org/browse/MRM-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRM-531: - Priority: Critical (was: Blocker) > Unable to download snapshots behind proxy with authentication > - > > Key: MRM-531 > URL: http://jira.codehaus.org/browse/MRM-531 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Affects Versions: 1.0-beta-2 > Environment: solaris 5.10, jdk1.6.0_02, proxy with basic > authentication >Reporter: Mathias Arens >Priority: Critical > Fix For: 1.0-beta-3 > > > I am able to download artifacts from several remote repositories into the > internal repository. But I cannot download any dependencies into the > snapshots repository. I always get a http-'Server redirected too many times > (20)'-error. I read that this error occurs if the proxy authentication > properties are not set correctly in the http client. I am behind a proxy with > basic authentication and an empty password. This configuration works fine for > the internal repository, but not for the snapshot repository. > Here are the logs: > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying > [cache-failures] policy with [ignored] > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures - OK to > fetch, check-failures policy set to IGNORED. > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying > [releases] policy with [disabled] > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.policies.PreDownloadPolicy:releases - OK to update, > release policy does not apply for snapshot versions. > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Applying > [snapshots] policy with [daily] > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,987 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.policies.PreDownloadPolicy:snapshots - OK to update > snapshots, local file does not exist. > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:08,988 > [SocketListener0-7] DEBUG > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - > Retrieving org/apache/maven/artifact/maven-artifact/3.0-SNAPSHOT/mave > n-artifact-3.0-SNAPSHOT.pom from Apache Snapshots Repository if updated > INFO | jvm 1| 2007/10/02 11:50:09 | 2007-10-02 11:50:09,087 > [SocketListener0-7] WARN > org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Download > failure:Error transferring file > INFO | jvm 1| 2007/10/02 11:50:09 | > org.apache.maven.wagon.TransferFailedException: Error transferring file > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:104) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:94) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferSimpleFile(DefaultRepositoryProxyConnectors.java:566) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.transferFile(DefaultRepositoryProxyConnectors.java:434) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:143) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.web.repository.ProxiedDavServer.applyServerSideRelocation(ProxiedDavServer.java:286) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.web.repository.ProxiedDavServer.fetchContentFromProxies(ProxiedDavServer.java:243) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:147) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119) > INFO | jvm 1| 2007/10/02 11:50:09 | at > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > INFO | jvm 1| 2007/10/02 11:50:09 | at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) > I
[jira] Commented: (MRM-481) Artifact requests with a .xml.zip extension fail with a 404 Error
[ http://jira.codehaus.org/browse/MRM-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109857 ] Brett Porter commented on MRM-481: -- was this fixed already? > Artifact requests with a .xml.zip extension fail with a 404 Error > - > > Key: MRM-481 > URL: http://jira.codehaus.org/browse/MRM-481 > Project: Archiva > Issue Type: Bug >Affects Versions: 1.0-beta-1 >Reporter: Cédric Vidal >Priority: Critical > Fix For: 1.0-beta-3 > > Attachments: multi-dots-ext-404-error.htm > > > This issue might also apply to any multi dots extension request but I didn't > check. > Regards, > Cédric -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (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:comment-tabpanel#action_109858 ] Brett Porter commented on MRM-535: -- wait, I'm confused. I don't believe the lastUpdated should reflect file timestamps at all - just using the ones from the proxied metadata (or the previous value in the file, since you can deploy directly to archiva). Highest value is right. If a value cannot be determined, just leave it out - Maven deals fine with that case - it's only looking for a delta. I'm not sure what you are referring to with project view / version view? > 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 >Assignee: Joakim Erdfelt >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] Commented: (MRM-459) prune the distributed dependencies
[ http://jira.codehaus.org/browse/MRM-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109859 ] Wendy Smoak commented on MRM-459: - Thanks, Brett. I put JSTL back in compile scope (by removing the scope=provided line) in r584468 and Archiva/Plexus Appserver works again. > prune the distributed dependencies > -- > > Key: MRM-459 > URL: http://jira.codehaus.org/browse/MRM-459 > Project: Archiva > Issue Type: Improvement > Components: web application >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > a large number of unneeded dependencies are distributed with Archiva (or if > they are needed, we might want to review why). > For example: ant-optional (probably for jsp compiler), commons-logging impl + > slf4j + log4j, xerces, jtidy, jdom, dom4j, commons-jxpath, jaxen, jta (we > have geronimo-jat already), classworlds (we have plexus-classworlds already), > backport (we require JDK 5, no need for this). > I'm also uncertain if all the maven libraries are still needed. -- 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-540) [regression] reports now show 0 results as a paged result that is empty
[regression] reports now show 0 results as a paged result that is empty --- Key: MRM-540 URL: http://jira.codehaus.org/browse/MRM-540 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-2 Reporter: Brett Porter in the past, I remember getting a good error message when the reports returned 0 results, but now I just get: Page: 1 >> The links do nothing. Also, I'm not sure why the text in the menu was changed to "pick report"? It's not like one is being selected for later use, and the other menu items under that menu are not verbs. -- 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: (MRM-468) incorrect URL reported from failures in WebDAV
[ http://jira.codehaus.org/browse/MRM-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MRM-468: -- try the URL you gave in a browser :) > incorrect URL reported from failures in WebDAV > -- > > Key: MRM-468 > URL: http://jira.codehaus.org/browse/MRM-468 > Project: Archiva > Issue Type: Bug > Components: WebDAV interface >Affects Versions: 1.0-beta-1 >Reporter: Brett Porter >Assignee: Joakim Erdfelt > Fix For: 1.0-beta-3 > > > eg. hit a URL that doesn't exist. The HTML response resembles: > Resource in error: > http://localhost:8080/archiva/repository/org/codehaus/cargo/cargo-ant/0.8/cargo-ant-0.8.jar/org/codehaus/cargo/cargo-ant/0.8/cargo-ant-0.8.jar > Note that the path is incorrect - it is appended again after .jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1521) NullPointerException in StarTeam changelog command
NullPointerException in StarTeam changelog command -- Key: CONTINUUM-1521 URL: http://jira.codehaus.org/browse/CONTINUUM-1521 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.1-beta-3 Environment: Linux RedHat ES3 Reporter: Stephen Cooper I get a NullPointerException when trying to build projects: Caused by: java.lang.NullPointerException at org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommand.executeChangeLogCommand(StarteamChangeLogCommand.java:57) at org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:101) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:75) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58) ... 16 more These same projects actually built OK several times, and now I'm getting this exception for all projects. This persists across restarts of continuum. These projects also build OK on continuum 1.0.3 -- 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-541) convenient way to take Archiva proxies "offline"
convenient way to take Archiva proxies "offline" Key: MRM-541 URL: http://jira.codehaus.org/browse/MRM-541 Project: Archiva Issue Type: Improvement Components: remote proxy Affects Versions: 1.0-beta-2 Reporter: Brett Porter I'm on a bad connection and proxying is very slow, making every archiva request a multiple of that slowness. I don't want to temporarily modify the configuration to disable the connectors (or even to turn on failure caching which would help a little) - but I would like to have an admin feature to temporarily turn off the proxy functionality altogether, considering Archiva "offline" (but still serving requests, not that kind of offline :). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1521) NullPointerException in StarTeam changelog command
[ http://jira.codehaus.org/browse/CONTINUUM-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109863 ] Stephen Cooper commented on CONTINUUM-1521: --- Playing a bit more with this...I have found out some things which may help. The project definition was set up to use the SCM credentials cache. When I disabled that option and re-entered my password, then the build started working. So, this bug might need to be re-worked and split into two separate issues: 1) get a better error message than NullPointerException for whatever was wrong with the SCM credential cache (minor) 2) SCM credential cache not working. (this one) > NullPointerException in StarTeam changelog command > -- > > Key: CONTINUUM-1521 > URL: http://jira.codehaus.org/browse/CONTINUUM-1521 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.1-beta-3 > Environment: Linux RedHat ES3 >Reporter: Stephen Cooper > > I get a NullPointerException when trying to build projects: > Caused by: java.lang.NullPointerException > at > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommand.executeChangeLogCommand(StarteamChangeLogCommand.java:57) > at > org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:101) > at > org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:75) > at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58) > ... 16 more > These same projects actually built OK several times, and now I'm getting this > exception for all projects. This persists across restarts of continuum. > These projects also build OK on continuum 1.0.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1521) NullPointerException in StarTeam changelog command
[ http://jira.codehaus.org/browse/CONTINUUM-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109871 ] Stephen Cooper commented on CONTINUUM-1521: --- More information - this issue re-occurs with working projects. I edit the project, enter my StarTeam password, the build works. Then, a while later, the build breaks with this exception. I go in and re-enter my password and the build works again. Irritating. > NullPointerException in StarTeam changelog command > -- > > Key: CONTINUUM-1521 > URL: http://jira.codehaus.org/browse/CONTINUUM-1521 > Project: Continuum > Issue Type: Bug > Components: SCM >Affects Versions: 1.1-beta-3 > Environment: Linux RedHat ES3 >Reporter: Stephen Cooper > > I get a NullPointerException when trying to build projects: > Caused by: java.lang.NullPointerException > at > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommand.executeChangeLogCommand(StarteamChangeLogCommand.java:57) > at > org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:101) > at > org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:75) > at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58) > ... 16 more > These same projects actually built OK several times, and now I'm getting this > exception for all projects. This persists across restarts of continuum. > These projects also build OK on continuum 1.0.3 -- 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
