[jira] Created: (MASSEMBLY-136) outputDirectory to support absolute paths
outputDirectory to support absolute paths - Key: MASSEMBLY-136 URL: http://jira.codehaus.org/browse/MASSEMBLY-136 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Affects Versions: 2.0.1 Environment: Linux Reporter: Kalle Korhonen Priority: Minor Can you please make the assembly parameter "outputDirectory" support absolute paths, just like "directory" in fileSets. Currently all paths are relative to the root directory of the assembly, whether or not you specify the path separator in the beginning or not. I see no reason why it should only support relative paths. I'm using assembly:directory to deploy some resources for my unit/integration tests that are normally available on a production environment. I realize I'm using the plugin "the wrong way", but the directory goal and format isn't suitable for deploying to the repository anyways. Also, either I don't know how to use appendAssemblyId correctly or it doesn't work for directory format. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPIR-55) Detailed Artifact Information & Repository Location for each Dependency.
[ http://jira.codehaus.org/browse/MPIR-55?page=comments#action_72194 ] Carlos Sanchez commented on MPIR-55: doesn't compile against latest maven-shared-jar C:\dev\maven\plugins\maven-project-info-reports-plugin\src\main\java\org\apache\maven\report\projectinfo\DependenciesReport.java:[512,38] cannot find symbol symbol : constructor Jar(java.io.File) location: class org.apache.maven.shared.jar.Jar C:\dev\maven\plugins\maven-project-info-reports-plugin\src\main\java\org\apache\maven\report\projectinfo\DependenciesReport.java:[513,53] cannot find symbol symbol : method analyzeClasses() location: class org.apache.maven.shared.jar.Jar > Detailed Artifact Information & Repository Location for each Dependency. > > > Key: MPIR-55 > URL: http://jira.codehaus.org/browse/MPIR-55 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature >Reporter: Joakim Erdfelt > Fix For: 2.1 > > Attachments: MPIR-55-dependencies-details-and-repo-locations.diff > > > I've created a patch that uses MNG-2489 (maven-shared-jar) and WAGON-58 > (wagon provider improvements) to increase the level of information about the > dependencies on the dependencies report. > Example Report: > http://joakim.erdfelt.com/maven-project-info-reports-plugin/dependencies.html > (See sections titled "Dependency File Details" and "Dependency Repository > Locations") > This adds the following information about each dependency. > * File size > * Count of entries > * Count of classes > * Count of packages > * JDK Revision of compiled classes > * If Debug is Present in compiled classes. > * If Jar is Sealed (in the manifest) > * What Repository the artifact can be found in > And adds a small section of all of the repositories in use by the project. -- 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: (WAGON-58) Implement .resourceExists(resourceName) and .getFileList(resourceDirectory) methods on all wagons.
[ http://jira.codehaus.org/browse/WAGON-58?page=all ] Carlos Sanchez closed WAGON-58. --- Assignee: Carlos Sanchez Resolution: Fixed Fix Version/s: 1.0-beta-2 Applied with some improvements and a new test case for getFileList when directory doesn't exist > Implement .resourceExists(resourceName) and .getFileList(resourceDirectory) > methods on all wagons. > -- > > Key: WAGON-58 > URL: http://jira.codehaus.org/browse/WAGON-58 > Project: wagon > Issue Type: New Feature >Reporter: Joakim Erdfelt > Assigned To: Carlos Sanchez > Fix For: 1.0-beta-2 > > Attachments: WAGON-58.diff > > > In order to provide some updated MPIR reports surrounding repository > information. > * Which repository does dependency/artifact exist on? > * Are there updates to the dependency/artifact available? > The wagon providers need to support 2 new methods. > * boolean Wagon.resourceExists(resourceName) > * List Wagon.getFileList(resourceName) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1029) fit-1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1029?page=comments#action_72192 ] Carlos Sanchez commented on MAVENUPLOAD-1029: - still doesn't follow instructions > fit-1.1 > > > Key: MAVENUPLOAD-1029 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1029 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Mauro Talevi > Assigned To: Carlos Sanchez > > Please upload fit-1.1.jar with POM > > 4.0.0 > fit > fit > Fit > 1.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MAVENUPLOAD-1029) fit-1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1029?page=all ] Mauro Talevi reopened MAVENUPLOAD-1029: --- Here's the URLs required: http://agilesque.net/dist/fit/jars/fit-1.1.jar http://agilesque.net/dist/fit/poms/fit-1.1.pom http://fit.c2.com Thanks! > fit-1.1 > > > Key: MAVENUPLOAD-1029 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1029 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Mauro Talevi > Assigned To: Carlos Sanchez > > Please upload fit-1.1.jar with POM > > 4.0.0 > fit > fit > Fit > 1.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (WAGON-47) add zip provider (source attahced)
[ http://jira.codehaus.org/browse/WAGON-47?page=comments#action_72188 ] John Didion commented on WAGON-47: -- Attachment #4 has everything, including tests and docs. For some reason, it didn't obsolete the other diffs with the same name. > add zip provider (source attahced) > -- > > Key: WAGON-47 > URL: http://jira.codehaus.org/browse/WAGON-47 > Project: wagon > Issue Type: New Feature > Components: wagon-provider-api >Reporter: John Didion > Attachments: wagon-provider-api.diff, wagon-provider-zip.diff, > wagon-provider-zip.diff, wagon-provider.zip.diff > > > As part of our build process, we generate repository snapshots contained > within a jar file. We have written an installer that is able to install > certain types of artifacts from any repository including a repository > snapshot jar. We needed to add a zip file provider to wagon so we could use > maven's repository api. It'd be nice to have that provider as part of wagon > proper. -- 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: (WAGON-47) add zip provider (source attahced)
[ http://jira.codehaus.org/browse/WAGON-47?page=all ] John Didion updated WAGON-47: - Attachment: wagon-provider.zip.diff > add zip provider (source attahced) > -- > > Key: WAGON-47 > URL: http://jira.codehaus.org/browse/WAGON-47 > Project: wagon > Issue Type: New Feature > Components: wagon-provider-api >Reporter: John Didion > Attachments: wagon-provider-api.diff, wagon-provider-zip.diff, > wagon-provider-zip.diff, wagon-provider.zip.diff > > > As part of our build process, we generate repository snapshots contained > within a jar file. We have written an installer that is able to install > certain types of artifacts from any repository including a repository > snapshot jar. We needed to add a zip file provider to wagon so we could use > maven's repository api. It'd be nice to have that provider as part of wagon > proper. -- 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: (MPARTIFACT-71) Can't deploy artifacts due to "reject HostKey" error
[ http://jira.codehaus.org/browse/MPARTIFACT-71?page=all ] Arnaud Heritier closed MPARTIFACT-71. - Assignee: Arnaud Heritier Resolution: Fixed It's fixed. Host key is always accepted. scpexe protocol works for me. If you encounter again this bug with scpexe, please open a new bug. > Can't deploy artifacts due to "reject HostKey" error > > > Key: MPARTIFACT-71 > URL: http://jira.codehaus.org/browse/MPARTIFACT-71 > Project: maven-artifact-plugin > Issue Type: Bug >Affects Versions: 1.8 > Environment: Client=Win XP; Maven 1.1b3; deploying tasks 1.3-snapshot > to maven-plugins at SourceForge >Reporter: Jeff Jensen > Assigned To: Arnaud Heritier >Priority: Blocker > Fix For: 1.8.1 > > > This is the high-level error info: > plugin:repository-deploy: > [echo] Deploying... > Will deploy to 1 repository(ies): maven.plugins.sf.snapshots > Deploying to repository: maven.plugins.sf.snapshots > Failed to deploy to: maven.plugins.sf.snapshots Reason: > org.apache.maven.wagon.authentication.AuthenticationException: Cannot > connect. Reason: reject HostKey: shell.sourceforge.net > org.apache.maven.wagon.authentication.AuthenticationException: Cannot > connect. Reason: reject HostKey: shell.sourceforge.net > at > org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(AbstractSshWagon.java:232) > If I use m1.1b3-snapshot of 6/30 from Arnaud's website, it works. Any > snapshot after that and the b3 release do not work - they have this problem. > I think (but not sure) one key procedure to reproducing this is to start with > clean repo and plugins install area: delete the .maven dir and any existing > Maven program dir (the plugins must start with only the bundled ones). -- 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-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_72186 ]
Baerrach bonDierne commented on MJAR-28:
In MASSEMBLY-67 John Casey says
The solution here is to use an outputFileNameMapping such as this:
${artifactId}-${baseVersion}.${extension}
Using ${baseVersion} for cases where you want to preserve the -SNAPSHOT naming,
the plugin retains the ability to use ${version} for the timestamp-buildnumber
naming, which is useful for describing the exact library version included in
the assembly.
(This issue can be closed)
> Using the jar plugin with addClasspath and snapshots can create manifest
> classpath with incorrect jar versions
> --
>
> Key: MJAR-28
> URL: http://jira.codehaus.org/browse/MJAR-28
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Mark J. Titorenko
> Attachments: MJAR-28-patch.txt
>
>
> When the POM contains dependencies to snapshot versions of jars, and snapshot
> versions of those jars are downloaded from a remote repository, the name of
> the jar contained in the classpath added to the manifest, of the form
> artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar
> downloaded, which contains version information of the form
> artifactID-X.X-MMDD.HHmmss-V.jar.
> This does not affect snapshot versions which have been directly installed
> into a local repository and have no uploaded version within the remote
> repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar
> form.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots
[ http://jira.codehaus.org/browse/MNG-2456?page=all ]
Baerrach bonDierne closed MNG-2456.
---
Resolution: Fixed
In MASSEMBLY-67 John Casey says
The solution here is to use an outputFileNameMapping such as this:
${artifactId}-${baseVersion}.${extension}
Using ${baseVersion} for cases where you want to preserve the -SNAPSHOT naming,
the plugin retains the ability to use ${version} for the timestamp-buildnumber
naming, which is useful for describing the exact library version included in
the assembly.
> Maven Archiver creates incorrect Class-Path entry in Manifest for deployed
> snapshots
>
>
> Key: MNG-2456
> URL: http://jira.codehaus.org/browse/MNG-2456
> Project: Maven 2
> Issue Type: Bug
> Components: maven-archiver
>Affects Versions: 2.0.4
>Reporter: Baerrach bonDierne
> Attachments: MNG-2456-patch.txt,
> MNG-2456-step1-refactoring-patch.txt,
> MNG-2456-step2-add-test-cases-patch.txt, MNG-2456-step3-fix-bug-patch.txt
>
>
> See related problems MJAR-28 and MASSEMBLY-67.
> Summary:
> The Maven-Archiver uses the file part of the artifact's filename to create
> the Class-Path entries in the Manifest.
> This works fine for released artifacts and non-deployed snapshot.
> The problem occurs when using a deployed snapshot as the assembly plugin will
> copy the dependency as ${artifactId}-${version}-timestampedversion.jar and
> the entry in the Class-Path will be ${artifactId}-${version}-SNAPSHOT
> thus use of java -jar will fail because of the differing names.
--
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-778) show internal error page on unhandled exceptions
[ http://jira.codehaus.org/browse/CONTINUUM-778?page=comments#action_72184 ] Jesse McConnell commented on CONTINUUM-778: --- I recently added a new baseclass in place of the PlexusActionSupport class on the trunk that does the initialization check that used to be on 1.0.3 where every page had a check to see if the continuum instance was initialized, and if it wasn't to redirect to the configuration edit screens... perhaps instead of chaining the exception itself from whatever action throws it, we could just add a method to that ContinuumActionSupport baseclass that logs the exception to the logger and then throw the exception normally for the exception interceptor to do its business... just a thought > show internal error page on unhandled exceptions > > > Key: CONTINUUM-778 > URL: http://jira.codehaus.org/browse/CONTINUUM-778 > Project: Continuum > Issue Type: Sub-task > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Carlos Sanchez > Assigned To: Napoleon Esmundo C. Ramirez > Fix For: 1.1 > > Attachments: CONTINUUM-778.patch, error-mapping.patch > > > It's possible to setup a servlet filter or something similar that maybe > webwork already has (Struts has it) to catch all unhandled exceptions, log > them to the log file and redirect the user to a "internal error" page. > Related to this we should make ContinuumException a RuntimeException, don't > catch it in the web layer and let the previous mechanism do it. We'll save a > lot of exception handling code not needed. > Note that this is only for system exceptions, eg. if database is down, and > not model exceptions, eg. when looking up by id it the record doesn't exist. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1032) IRCLib from org.schwering
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1032?page=comments#action_72181 ] Andrew Williams commented on MAVENUPLOAD-1032: -- Many apologies - I must have been very tired at the time the correct URL is: http://maven.rectang.com/irclib-1.04-bsd_uploadbundle.jar > IRCLib from org.schwering > - > > Key: MAVENUPLOAD-1032 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1032 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andrew Williams > > IRClib is a free Java implementation of the IRC protocol. > The upload is needed to support some new Plexus IRC features :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1032) IRCLib from org.schwering
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1032?page=comments#action_72180 ] Carlos Sanchez commented on MAVENUPLOAD-1032: - what you linked http://maven.rectang.com/irclib-1.04-bsd.jar is not a bundle as said in the instructions, it's just the jar > IRCLib from org.schwering > - > > Key: MAVENUPLOAD-1032 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1032 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andrew Williams > > IRClib is a free Java implementation of the IRC protocol. > The upload is needed to support some new Plexus IRC features :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1032) IRCLib from org.schwering
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1032?page=comments#action_72178 ] Andrew Williams commented on MAVENUPLOAD-1032: -- The pom.xml is insie the jar, as dictated by http://maven.apache.org/guides/mini/guide-ibiblio-upload.html > IRCLib from org.schwering > - > > Key: MAVENUPLOAD-1032 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1032 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andrew Williams > > IRClib is a free Java implementation of the IRC protocol. > The upload is needed to support some new Plexus IRC features :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1030) Please upload json-lib-0.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1030?page=comments#action_72176 ] Andres Almiray commented on MAVENUPLOAD-1030: - Maven's repository plugin doesn't seem to work on my config, created the jar manually. json-lib-0.7.1 is the latest release http://json-lib.sourceforge.net/json-lib-0.7.1-bundle.jar > Please upload json-lib-0.6 > -- > > Key: MAVENUPLOAD-1030 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1030 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andres Almiray > > JSON-lib is a java library for transforming beans, maps and XML to JSON and > back again to beans and DynaBeans. > Javadocs are at http://json-lib.sourceforge.net/json-lib-0.6-javadoc.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MWAR-59) artifact extension set incorrectly in a multi-module build
[ http://jira.codehaus.org/browse/MWAR-59?page=all ] Andreas Wuest updated MWAR-59: -- Attachment: ejb-client-test-patch.txt patch for the corresponding test case > artifact extension set incorrectly in a multi-module build > -- > > Key: MWAR-59 > URL: http://jira.codehaus.org/browse/MWAR-59 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.0.1 >Reporter: Brett Porter > Fix For: 2.0.2 > > Attachments: ejb-client-patch.txt, ejb-client-test-patch.txt > > > from the list... > unfortunately [MWAR-38] is not fully fixed - It still does not work in a > multi-module build. > We do have here the following structure: > root > jarmodule > ejb > webapp > Running a "mvn package" inside the webapp module, the EJB-Client jar from > the ejb module is resolved correctly and copied to WEB-INF/lib with the > correct ".jar" ending. > Running the "mvn package" from the root module, the ejb-client jar from the > ejb module is resolved but copied with a ".ejb-client" ending, and not with > ".jar". > You can test this by using the "daytrader" example from the Maven book. -- 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: (MWAR-59) artifact extension set incorrectly in a multi-module build
[ http://jira.codehaus.org/browse/MWAR-59?page=all ] Andreas Wuest updated MWAR-59: -- Attachment: ejb-client-patch.txt patch for the ejb-client > artifact extension set incorrectly in a multi-module build > -- > > Key: MWAR-59 > URL: http://jira.codehaus.org/browse/MWAR-59 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.0.1 >Reporter: Brett Porter > Fix For: 2.0.2 > > Attachments: ejb-client-patch.txt, ejb-client-test-patch.txt > > > from the list... > unfortunately [MWAR-38] is not fully fixed - It still does not work in a > multi-module build. > We do have here the following structure: > root > jarmodule > ejb > webapp > Running a "mvn package" inside the webapp module, the EJB-Client jar from > the ejb module is resolved correctly and copied to WEB-INF/lib with the > correct ".jar" ending. > Running the "mvn package" from the root module, the ejb-client jar from the > ejb module is resolved but copied with a ".ejb-client" ending, and not with > ".jar". > You can test this by using the "daytrader" example from the Maven book. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-59) artifact extension set incorrectly in a multi-module build
[ http://jira.codehaus.org/browse/MWAR-59?page=comments#action_72173 ] Andreas Wuest commented on MWAR-59: --- Still having this problem. the following post will contain a patch, at least for the "ejb-client" type in the dependency. so here is what i found out. With the latest cvs snapshot it is not possible to add the ejb client to the war, always the ejb.jar will be added to the war file what is not really inteded. the project looks like : Parent - Project A (Ejb) - Project B (War) this dependency will only add the ejb(server).jar to the war file. What i really want is that the created ejb-client.jar is added to the war. adding the ejb(server).jar to the war file does not make sense for the war file. (the maven-ejb-plugin created a server and client version for the de.blubb.project_name.ejb projekt, which is actually another module of my project) de.blubb.project_name ejb 1.0 ejb-client If the patch is obsolete, i was wondering if there is anybody out there who is using the maven-ejb-plugin in combination with the maven-war-plugin and is actually adding the created ejb-client to the created war file successfully. As far as i can tell the maven-ejb-plugin creates a client (if requested) with the name --client.jar. however the maven-war-plugin does not respect the "-client" in the client's name. even if i set the "type" of the dependency to "ejb-client" it is still getting the "ejb.jar", not the "ejb-client.jar". My patch fixes this problem. i can provide a testcase that shows the current problem, if requested. sorry for the long comment. > artifact extension set incorrectly in a multi-module build > -- > > Key: MWAR-59 > URL: http://jira.codehaus.org/browse/MWAR-59 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0, 2.0.1 >Reporter: Brett Porter > Fix For: 2.0.2 > > Attachments: ejb-client-patch.txt, ejb-client-test-patch.txt > > > from the list... > unfortunately [MWAR-38] is not fully fixed - It still does not work in a > multi-module build. > We do have here the following structure: > root > jarmodule > ejb > webapp > Running a "mvn package" inside the webapp module, the EJB-Client jar from > the ejb module is resolved correctly and copied to WEB-INF/lib with the > correct ".jar" ending. > Running the "mvn package" from the root module, the ejb-client jar from the > ejb module is resolved but copied with a ".ejb-client" ending, and not with > ".jar". > You can test this by using the "daytrader" example from the Maven book. -- 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: (MANTRUN-58) Update depencies to include all ant artifacts so all ant tasks can be used
Update depencies to include all ant artifacts so all ant tasks can be used -- Key: MANTRUN-58 URL: http://jira.codehaus.org/browse/MANTRUN-58 Project: Maven 2.x Antrun Plugin Issue Type: Bug Reporter: Jason Chaffee Priority: Blocker Should add ALL ant distribution artifacts as dependencies as some tasks cannot be run without them. For example, ant-trax is needed to use with the trax processor. -- 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: (MSITE-155) site:run does not work with upper case letters in
[ http://jira.codehaus.org/browse/MSITE-155?page=all ] Vincent Siveton closed MSITE-155. - Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.0 Fixed in doxia-site-renderer > site:run does not work with upper case letters in > -- > > Key: MSITE-155 > URL: http://jira.codehaus.org/browse/MSITE-155 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 > Environment: WindowsXP >Reporter: Ted Husted > Assigned To: Vincent Siveton > Fix For: 2.0 > > > If a file or folder name contains an uppercase letter, the site:run plugin > will return HTTP ERROR: 404 - NOT_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: (WAGON-58) Implement .resourceExists(resourceName) and .getFileList(resourceDirectory) methods on all wagons.
[ http://jira.codehaus.org/browse/WAGON-58?page=all ] Joakim Erdfelt updated WAGON-58: Attachment: (was: WAGON-58.diff) > Implement .resourceExists(resourceName) and .getFileList(resourceDirectory) > methods on all wagons. > -- > > Key: WAGON-58 > URL: http://jira.codehaus.org/browse/WAGON-58 > Project: wagon > Issue Type: New Feature >Reporter: Joakim Erdfelt > Attachments: WAGON-58.diff > > > In order to provide some updated MPIR reports surrounding repository > information. > * Which repository does dependency/artifact exist on? > * Are there updates to the dependency/artifact available? > The wagon providers need to support 2 new methods. > * boolean Wagon.resourceExists(resourceName) > * List Wagon.getFileList(resourceName) -- 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: (WAGON-58) Implement .resourceExists(resourceName) and .getFileList(resourceDirectory) methods on all wagons.
[ http://jira.codehaus.org/browse/WAGON-58?page=all ] Joakim Erdfelt updated WAGON-58: Attachment: WAGON-58.diff Updated patch WAGON-58 to correct 2 tests cases. > Implement .resourceExists(resourceName) and .getFileList(resourceDirectory) > methods on all wagons. > -- > > Key: WAGON-58 > URL: http://jira.codehaus.org/browse/WAGON-58 > Project: wagon > Issue Type: New Feature >Reporter: Joakim Erdfelt > Attachments: WAGON-58.diff > > > In order to provide some updated MPIR reports surrounding repository > information. > * Which repository does dependency/artifact exist on? > * Are there updates to the dependency/artifact available? > The wagon providers need to support 2 new methods. > * boolean Wagon.resourceExists(resourceName) > * List Wagon.getFileList(resourceName) -- 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: (MAVENUPLOAD-1039) jpox: wrong "pom~"
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1039?page=all ] Carlos Sanchez closed MAVENUPLOAD-1039. --- Assignee: Carlos Sanchez Resolution: Fixed > jpox: wrong "pom~" > -- > > Key: MAVENUPLOAD-1039 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1039 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Rainer Wasserfuhr > Assigned To: Carlos Sanchez > > this file should be deleted. -- 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: (MAVENUPLOAD-1040) remove unused folder "not-really-jelly/commons-jelly/"
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1040?page=all ] Carlos Sanchez closed MAVENUPLOAD-1040. --- Assignee: Carlos Sanchez Resolution: Fixed > remove unused folder "not-really-jelly/commons-jelly/" > -- > > Key: MAVENUPLOAD-1040 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1040 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Rainer Wasserfuhr > Assigned To: Carlos Sanchez > > http://www.ibiblio.org/maven2/not-really-jelly/commons-jelly/ is empty, > so both > http://www.ibiblio.org/maven2/not-really-jelly/commons-jelly/ and > http://www.ibiblio.org/maven2/not-really-jelly > could be removed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1035) POM for wstx-asl-2.9.3 is missing
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1035?page=comments#action_72168 ] Carlos Sanchez commented on MAVENUPLOAD-1035: - missing required info: dependencies, license,... > POM for wstx-asl-2.9.3 is missing > - > > Key: MAVENUPLOAD-1035 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1035 > Project: maven-upload-requests > Issue Type: Bug >Reporter: Jochen Wiedmann > > The directory > http://repo1.maven.org/maven2/woodstox/wstx-asl/2.9.3 > does not contain a POM. This jar file is referenced by popular applications > like Axis2-1.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1036) Upload axiom-1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1036?page=all ] Carlos Sanchez closed MAVENUPLOAD-1036. --- Assignee: Carlos Sanchez Resolution: Won't Fix Apache artifacts must be deployed through apache repo, contact repository@apache.org ofr questions > Upload axiom-1.0 > > > Key: MAVENUPLOAD-1036 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1036 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Jochen Wiedmann > Assigned To: Carlos Sanchez > > Axiom 1.0 is used by popular packages like Axis2-1.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1038) Upload neethi-1.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1038?page=all ] Carlos Sanchez closed MAVENUPLOAD-1038. --- Assignee: Carlos Sanchez Resolution: Won't Fix Apache artifacts must be deployed through apache repo, contact repository@apache.org for questions > Upload neethi-1.0.1 > --- > > Key: MAVENUPLOAD-1038 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1038 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Jochen Wiedmann > Assigned To: Carlos Sanchez > > Neethi 1.0.1 is used by popular packages like Axis2-1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1041) Glazed Lists 1.7.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1041?page=all ] Carlos Sanchez closed MAVENUPLOAD-1041. --- Assignee: Carlos Sanchez Resolution: Fixed > Glazed Lists 1.7.0 > -- > > Key: MAVENUPLOAD-1041 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1041 > Project: maven-upload-requests > Issue Type: Task >Reporter: Jesse Wilson > Assigned To: Carlos Sanchez > > Glazed Lists 1.7.0 - an improvement release - with better event firing, > autocomplete, and builds (Ant and Maven). It also fixes crucial performance > bugs and adds a multimap feature. -- 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: (MAVENUPLOAD-1034) missing spring poms
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1034?page=all ] Carlos Sanchez closed MAVENUPLOAD-1034. --- Assignee: Carlos Sanchez Resolution: Won't Fix Refer to http://opensource.atlassian.com/projects/spring/browse/SPR-1484 > missing spring poms > --- > > Key: MAVENUPLOAD-1034 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1034 > Project: maven-upload-requests > Issue Type: Improvement >Reporter: Rainer Wasserfuhr > Assigned To: Carlos Sanchez > > many versions at http://www.ibiblio.org/maven2/org/springframework/spring/ > do not have poms, e.g. > http://www.ibiblio.org/maven2/org/springframework/spring/1.2/ > or > http://www.ibiblio.org/maven2/org/springframework/spring/2.0-rc2/ > 2.0-rc2 is missing 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: (MAVENUPLOAD-1033) Please upload JBoss Cache Version 1.4.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1033?page=comments#action_72164 ] Carlos Sanchez commented on MAVENUPLOAD-1033: - Please read the instructions http://maven.apache.org/guides/mini/guide-ibiblio-upload.html > Please upload JBoss Cache Version 1.4.0 > --- > > Key: MAVENUPLOAD-1033 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1033 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Alex Rau > > Reason: the existing version 1.2.2 in the central maven repository is pretty > old. > The bundle url points to the distribution bundle which contains several other > jars from JBoss and other projects which probably need to be deployed and > referenced by dependencies as well. > Tnx and regards -- 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: (MRELEASE-148) Add prompts to input parent POM release version and next development version
Add prompts to input parent POM release version and next development version Key: MRELEASE-148 URL: http://jira.codehaus.org/browse/MRELEASE-148 Project: Maven 2.x Release Plugin Issue Type: New Feature Reporter: Eric Berry Priority: Minor We have a master POM file that we use as a parent for all our other POM that I always release build first. It is annoying to modify the child POM to reference the new released parent POM version before I do the release and afterwards to set the next parent POM version. The child POMs are NOT included as a module in the parent POM. The plugin currently works as expected when the child POM references the parent POM and the parent POM references the child POM and you run the release from the parent POM. -- 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: (MAVENUPLOAD-1029) fit-1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1029?page=all ] Carlos Sanchez closed MAVENUPLOAD-1029. --- Assignee: Carlos Sanchez Resolution: Incomplete > fit-1.1 > > > Key: MAVENUPLOAD-1029 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1029 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Mauro Talevi > Assigned To: Carlos Sanchez > > Please upload fit-1.1.jar with POM > > 4.0.0 > fit > fit > Fit > 1.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1030) Please upload json-lib-0.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1030?page=comments#action_72163 ] Carlos Sanchez commented on MAVENUPLOAD-1030: - javadoc must be inside same bundle > Please upload json-lib-0.6 > -- > > Key: MAVENUPLOAD-1030 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1030 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andres Almiray > > JSON-lib is a java library for transforming beans, maps and XML to JSON and > back again to beans and DynaBeans. > Javadocs are at http://json-lib.sourceforge.net/json-lib-0.6-javadoc.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] Commented: (MAVENUPLOAD-1032) IRCLib from org.schwering
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1032?page=comments#action_72162 ] Carlos Sanchez commented on MAVENUPLOAD-1032: - Cannot deploy without the pom.xml or project.xml file! > IRCLib from org.schwering > - > > Key: MAVENUPLOAD-1032 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1032 > Project: maven-upload-requests > Issue Type: Task >Reporter: Andrew Williams > > IRClib is a free Java implementation of the IRC protocol. > The upload is needed to support some new Plexus IRC features :) -- 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: (MAVENUPLOAD-1043) Upload fastutil-5.0.4 to ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1043?page=all ] Carlos Sanchez closed MAVENUPLOAD-1043. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload fastutil-5.0.4 to ibiblio > > > Key: MAVENUPLOAD-1043 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1043 > Project: maven-upload-requests > Issue Type: Task >Reporter: Matt Whitlock > Assigned To: Carlos Sanchez > > http://www.mattwhitlock.com/fastutil-5.0.4-bundle.jar > http://fastutil.dsi.unimi.it/ > fastutil extends the Java Collections Framework by providing type-specific > maps, sets, lists and queues with a small memory footprint and fast access > and insertion; it also includes a fast I/O API for binary and text files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2016) Document how to create a mirror of Ibiblio
[ http://jira.codehaus.org/browse/MNG-2016?page=comments#action_72160 ] Carlos Sanchez commented on MNG-2016: - The command to create a mirror is rsync -v -t -l -r ftp.ibiblio.org::maven2 /your/local/path > Document how to create a mirror of Ibiblio > -- > > Key: MNG-2016 > URL: http://jira.codehaus.org/browse/MNG-2016 > Project: Maven 2 > Issue Type: Task > Components: Artifacts and Repositories, Documentation: General >Reporter: Trygve Laugstol > Fix For: 2.1 > > > Tips on what this document could include: > o Find a pointer to the list of Ibiblio mirrors > o Give an example command line for at least rsync, wget and curl where the > two last ones will use ftp > o Give an example cron expression and /etc/cron.d/ file that's useful for > making a mirrors including setting the correct permissions > o Give an example Apache configuration on how to configure Apache to serve > the mirror > This document should possibly be a part of > http://maven.apache.org/guides/mini/guide-mirror-settings.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] Created: (MNG-2496) dependencyManagement not used for dependencies in plugin section.
dependencyManagement not used for dependencies in plugin section.
-
Key: MNG-2496
URL: http://jira.codehaus.org/browse/MNG-2496
Project: Maven 2
Issue Type: Bug
Components: Artifacts
Affects Versions: 2.0.4
Reporter: Brian Fox
In my parent, I have a dependencyManagement set with this jar:
com.stchome.build.maven
testng-initializer
1.0
test
I have a plugin specified that had a dependency like this:
maven-antrun-plugin
run-testng
test
run
com.stchome.build.maven
testng-initializer
When I build, it doesn't seem to resolve this dependency version from
dependencyManagement
[INFO] An invalid artifact was detected.
This artifact might be in your project's POM, or it might have been included
transitively du
information we do have for this artifact:
o GroupID: com.stchome.build.maven
o ArtifactID: testng-initializer
o Version: <<< MISSING >>>
o Type:jar
[INFO]
[INFO] Trace
org.apache.maven.artifact.InvalidArtifactRTException: For artifact
{com.stchome.build.maven:
n cannot be empty.
at
org.apache.maven.artifact.DefaultArtifact.validateIdentity(DefaultArtifact.java:1
at
org.apache.maven.artifact.DefaultArtifact.(DefaultArtifact.java:119)
at
org.apache.maven.artifact.factory.DefaultArtifactFactory.createArtifact(DefaultAr
at
org.apache.maven.artifact.factory.DefaultArtifactFactory.createDependencyArtifact
at
org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetada
at
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:
at
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginM
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.ja
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycle
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(Default
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(De
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleE
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLi
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecu
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2129) generated source repo page is misleading when added to the "general site".
[ http://jira.codehaus.org/browse/MNG-2129?page=all ] Vincent Siveton closed MNG-2129. Assignee: Vincent Siveton Resolution: Fixed Applied in svn with brett suggestions Thanks. > generated source repo page is misleading when added to the "general site". > -- > > Key: MNG-2129 > URL: http://jira.codehaus.org/browse/MNG-2129 > Project: Maven 2 > Issue Type: Improvement > Components: Design, Patterns & Best Practices, Documentation: > General >Reporter: Brett Porter > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > Attachments: MNG-2129-maven-site.patch > > > it says: > $ svn checkout http://svn.apache.org/repos/asf/maven/components/trunk/ > maven-site > We really should set the SCM URL correctly in the site pom again (to point to > the site SCM), and the generated report should be excluded from the > navigation. It could still be generated and linked from another doc that > describes helping with the docs. -- 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: (MASSEMBLY-88) Use test harness for the assembly plugin
[ http://jira.codehaus.org/browse/MASSEMBLY-88?page=all ] John Casey closed MASSEMBLY-88. --- Assignee: John Casey (was: Edwin Punzalan) Resolution: Won't Fix Fix Version/s: 2.2 we're not using the test harness for the assembly plugin now that it's refactored. The invoker plugin and plugin-test plugin, combined with conventional unit tests that use mock objects, is enough now. It's also much more maintainable. > Use test harness for the assembly plugin > > > Key: MASSEMBLY-88 > URL: http://jira.codehaus.org/browse/MASSEMBLY-88 > Project: Maven 2.x Assembly Plugin > Issue Type: Test >Affects Versions: 2.1 >Reporter: Edwin Punzalan > Assigned To: John Casey > Fix For: 2.2 > > Attachments: maven-assembly-plugin-tests.patch > > -- 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-1043) Upload fastutil-5.0.4 to ibiblio
Upload fastutil-5.0.4 to ibiblio Key: MAVENUPLOAD-1043 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1043 Project: maven-upload-requests Issue Type: Task Reporter: Matt Whitlock http://www.mattwhitlock.com/fastutil-5.0.4-bundle.jar http://fastutil.dsi.unimi.it/ fastutil extends the Java Collections Framework by providing type-specific maps, sets, lists and queues with a small memory footprint and fast access and insertion; it also includes a fast I/O API for binary and text files. -- 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: (MASSEMBLY-112) project artifact included in dependencies
[ http://jira.codehaus.org/browse/MASSEMBLY-112?page=all ] John Casey closed MASSEMBLY-112. Assignee: John Casey Resolution: Fixed fixed during refactor, and verified by IT: dependency-sets/dependencySet-projectArtifactNotIncluded > project artifact included in dependencies > - > > Key: MASSEMBLY-112 > URL: http://jira.codehaus.org/browse/MASSEMBLY-112 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Martijn Dashorst > Assigned To: John Casey > Fix For: 2.2 > > Attachments: foo.zip > > > The dependency set for a war packaged project includes the final war file > into the dependencies. There is no way to exclude it. > The attached zip file shows a project which exibits this behavior. > The final zip contains the following structure: > foo/pom.xml > foo/lib > foo/lib/commons-logging-1.0.4.jar > foo/lib/foo.war > foo/src > foo/src/assembly > foo/src/assembly/bin.xml > foo/src/main > and several source files (left them out for brevity). Please note that the > assembly includes the final war file in the lib directory, where it doesn't > belong. Also note that the servlet api dependency is not included (see other > issue). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2291) svn ignore command incorrect
[ http://jira.codehaus.org/browse/MNG-2291?page=all ] Vincent Siveton closed MNG-2291. Assignee: Vincent Siveton Resolution: Fixed Applied. Thanks > svn ignore command incorrect > > > Key: MNG-2291 > URL: http://jira.codehaus.org/browse/MNG-2291 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Guides >Affects Versions: 2.0.4 >Reporter: Jerome Lacoste > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > Attachments: patch.txt > > > > svn propset . svn:ignore -F ~/Documents/svnignore.txt > svn: Bad property name: '.' > > svn propset svn:ignore -F ~/Documents/svnignore.txt . > property 'svn:ignore' set on '.' > > svn --version > svn, version 1.3.1 (r19032) >compiled May 6 2006, 00:19:28 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2311) site plugin i18n HU
[ http://jira.codehaus.org/browse/MNG-2311?page=all ] Vincent Siveton closed MNG-2311. Assignee: Vincent Siveton Resolution: Fixed Applied. Thanks. > site plugin i18n HU > --- > > Key: MNG-2311 > URL: http://jira.codehaus.org/browse/MNG-2311 > Project: Maven 2 > Issue Type: Improvement > Components: Sites & Reporting >Reporter: Laszlo Hornyak Kocka > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > Attachments: project-info-report_hu.properties, > project-info-report_hu.properties, site-plugin_hu.properties > > > hungarian translation of the resource files as described in > http://maven.apache.org/plugins/maven-site-plugin/i18n.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-148) provide way of zipping the repository index for remote distribution
[ http://jira.codehaus.org/browse/MRM-148?page=comments#action_72148 ] Milos Kleint commented on MRM-148: -- i figured the current patch is not 100% functional. the zipped index is placed in the local repository (from configuration store. That's what I thought to be the location of the maven repository. However it seems it's not that case. I guess there's a conceptual problem with this a bit. The index can be shared among multiple repositories that are managed by the webapp. The "let's have a zipped index in the repository root" idea is not compatible with this setup. There is not a 1:1 relationship between the index and the repository. > provide way of zipping the repository index for remote distribution > --- > > Key: MRM-148 > URL: http://jira.codehaus.org/browse/MRM-148 > Project: Maven Repository Manager > Issue Type: New Feature >Reporter: Milos Kleint > Attachments: archiver.patch > > > for use in the IDEs, it would be nice to have the index for the remote > repository readily available for download. the attached path solves that by > always creating a zip file after the index is updated and placing it into the > repository in .index folder. That way the IDE can easily check the location > only with the knowledge of the repository url. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2355) Documentation of the @component javadoc tag
[ http://jira.codehaus.org/browse/MNG-2355?page=all ] Vincent Siveton closed MNG-2355. Assignee: Vincent Siveton Resolution: Fixed Fixed in svn > Documentation of the @component javadoc tag > --- > > Key: MNG-2355 > URL: http://jira.codehaus.org/browse/MNG-2355 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: General >Reporter: Scott Cytacki > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > > While trying to figure out how the AbstractCompilerMojo worked, I found the > @component tag for the compilerManager field. There is a reference page for > the mojo-api-spec, but this page doesn't talk about the "component" tag. > That page seems like a logical place to put this documentation, or at least a > reference to it if it is already somewhere else. -- 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: (MASSEMBLY-107) DependencySet does not support classifier
[ http://jira.codehaus.org/browse/MASSEMBLY-107?page=all ] John Casey updated MASSEMBLY-107: - Description: true someGroupId:someArtifactid:someClassifier Currently the depedencySetProcessing does not expect to handle classifier was: true someGroupId:someArtifactid:someClassifier Currently the depedencySetProcessing does not expect to handle classifier Issue Type: Improvement (was: Bug) > DependencySet does not support classifier > -- > > Key: MASSEMBLY-107 > URL: http://jira.codehaus.org/browse/MASSEMBLY-107 > Project: Maven 2.x Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.1 > Environment: xp >Reporter: Dan Tran > Fix For: 2.2 > > > > > true > > someGroupId:someArtifactid:someClassifier > > > Currently the depedencySetProcessing does not expect to handle classifier -- 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: (MASSEMBLY-91) Currently the assembly plugin renames SNAPSHOT dependencies to a date stamp ex. api-authorisation-4.00-20060502.150651-20.jar
[ http://jira.codehaus.org/browse/MASSEMBLY-91?page=all ]
John Casey closed MASSEMBLY-91.
---
Assignee: John Casey (was: Brett Porter)
Resolution: Fixed
The solution here is to use an outputFileNameMapping such as this:
${artifactId}-${baseVersion}.${extension}
Using ${baseVersion} for cases where you want to preserve the -SNAPSHOT naming,
the plugin retains the ability to use ${version} for the timestamp-buildnumber
naming, which is useful for describing the exact library version included in
the assembly.
I've added an integration test:
/basic-features/outputFileNameMapping-withArtifactBaseVersion to verify that
this is fixed.
> Currently the assembly plugin renames SNAPSHOT dependencies to a date stamp
> ex. api-authorisation-4.00-20060502.150651-20.jar
> -
>
> Key: MASSEMBLY-91
> URL: http://jira.codehaus.org/browse/MASSEMBLY-91
> Project: Maven 2.x Assembly Plugin
> Issue Type: New Feature
>Affects Versions: 2.0.1
> Environment: Win XP, Java 1.5
>Reporter: Chris Stevenson
> Assigned To: John Casey
> Fix For: 2.2
>
>
> Currently the assembly plugin renames SNAPSHOT dependencies to a date stamp
> ex. api-authorisation-4.00-20060502.150651-20.jar. Would it be possible to
> offer a flag on the plugin so that this behaviour could be turned off and the
> file could remain as api-authorisation-SNAPSHOT.jar?
> The renaming of the files causes the files to become invalid when compiling
> native or CSharp binaries inside of maven.
> Thanks,
> Chris Stevenson
--
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: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}
[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=all ]
John Casey closed MASSEMBLY-67.
---
Assignee: John Casey
Resolution: Fixed
The solution here is to use an outputFileNameMapping such as this:
${artifactId}-${baseVersion}.${extension}
Using ${baseVersion} for cases where you want to preserve the -SNAPSHOT naming,
the plugin retains the ability to use ${version} for the timestamp-buildnumber
naming, which is useful for describing the exact library version included in
the assembly.
I've added an integration test:
/basic-features/outputFileNameMapping-withArtifactBaseVersion to verify that
this is fixed.
> assembling dependent jars or snapshots uses timestamp formatted version
> instead of ${version}
> -
>
> Key: MASSEMBLY-67
> URL: http://jira.codehaus.org/browse/MASSEMBLY-67
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Reporter: Mark J. Titorenko
> Assigned To: John Casey
> Fix For: 2.2
>
> Attachments: MJAR-28-Notes.txt, MJAR-28-TestCases-Patch.txt
>
>
> I'm using the jar plugin to add my dependencies to the manifest. I'm also
> using the assembly plugin to package all dependencies into one archive. The
> problem is that the jar manifest adds my dependencies as "foo-SNAPHOT" and
> the archiver adds them as "foo-20041113.jar".
> This causes my snapshot classes to not be found at runtime.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEJB-19) clientExclude(s) does not work
clientExclude(s) does not work -- Key: MEJB-19 URL: http://jira.codehaus.org/browse/MEJB-19 Project: Maven 2.x Ejb Plugin Issue Type: Bug Affects Versions: 2.0 Environment: Maven 2.0.4 Reporter: Stefan Seidel I've tried each and every configuration of and to control what is being put into the ejb-client JAR, but nothing really works. I expect the configuration ** to produce an empty JAR - but it doesn't. What I really need to do is to exclude ejb-jar.xml and jboss.xml from the client jar because JBoss 4 will still (try to) deploy the JAR file because these XMLs are in it, even if it is given as java module in the application.xml. Leaving these files there leads the whole idea of a client JAR ad adsurdum. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1459) guide for creating ejb and corresponding ejb client JAR
[ http://jira.codehaus.org/browse/MNG-1459?page=comments#action_72143 ] David J. M. Karlsen commented on MNG-1459: -- This seems to be fixed? http://maven.apache.org/plugins/maven-ejb-plugin/howto.html > guide for creating ejb and corresponding ejb client JAR > --- > > Key: MNG-1459 > URL: http://jira.codehaus.org/browse/MNG-1459 > Project: Maven 2 > Issue Type: Task > Components: Documentation: Guides >Reporter: Jason van Zyl > Fix For: 2.0.5 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1370) Guide to attached artifacts
[ http://jira.codehaus.org/browse/MNG-1370?page=comments#action_72142 ] David J. M. Karlsen commented on MNG-1370: -- Is this still an issue?: http://maven.apache.org/guides/mini/guide-attached-tests.html and http://maven.apache.org/plugins/maven-ejb-plugin/howto.html > Guide to attached artifacts > --- > > Key: MNG-1370 > URL: http://jira.codehaus.org/browse/MNG-1370 > Project: Maven 2 > Issue Type: Task > Components: Documentation: Guides >Reporter: Jason van Zyl > Fix For: 2.0.5 > > > Show how to use attached artifacts like source bundles and javadocs, and the > use the ejb plugin which creates the ejb-client attached artiact. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2407) New user docs: proxy configuration is not clear to new users
[ http://jira.codehaus.org/browse/MNG-2407?page=all ] Vincent Siveton closed MNG-2407. Assignee: Vincent Siveton Resolution: Fixed Added a link to Configuring Maven > New user docs: proxy configuration is not clear to new users > > > Key: MNG-2407 > URL: http://jira.codehaus.org/browse/MNG-2407 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: Guides >Affects Versions: 2.0.4 >Reporter: Graham Leggett > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > > When setting up maven v2.0.4 from the perspective of a new user, I have the > need to use a proxy. > Looking for proxy in the docs finds this first: > http://maven.apache.org/guides/mini/guide-proxies.html > This explains how to add proxy information to a "settings file", but does not > clearly describe what a > "settings file" is. The page does give a clue though, by linking the user > here: http://maven.apache.org/maven-settings/settings.html > This document contains the full definition of what goes into a settings file, > but gives no clue as to where > this settings file should live, or what it should be called. > At this point I have hit a dead end, as a new maven v2 user, there are no > more clues on how to set up a proxy. > The docs need to be updated to link to information on where the settings file > lives, and what the settings file is called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2453) Site plugin NO locale
[ http://jira.codehaus.org/browse/MNG-2453?page=comments#action_72140 ] David J. M. Karlsen commented on MNG-2453: -- Oh - didn't see that - thanks for the information - the guy is even one I work with - lol :-) I saw Trygvis added the other one - so attachment 1. can be skipped. Still, I'll try to add info translation soon. > Site plugin NO locale > - > > Key: MNG-2453 > URL: http://jira.codehaus.org/browse/MNG-2453 > Project: Maven 2 > Issue Type: Improvement > Components: Sites & Reporting > Environment: N/A >Reporter: David J. M. Karlsen >Priority: Minor > Attachments: site-plugin_no.properties > > > Norwegian (bokmål - NO_nb) translation. > I'll add "info" translation soon -- 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: (MWAR-68) CLONE -Overlay war can overwrite main project web.xml
[ http://jira.codehaus.org/browse/MWAR-68?page=all ] Brett Porter closed MWAR-68. Resolution: Duplicate Fix Version/s: (was: 2.0.2) the fixed release - 2.0.2 - of the war plugin (nothing to do with the maven core) has not been released. Duplicate of the originally cloned issue. > CLONE -Overlay war can overwrite main project web.xml > - > > Key: MWAR-68 > URL: http://jira.codehaus.org/browse/MWAR-68 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.1 >Reporter: Stefan Seidel > Assigned To: Brett Porter > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 1) overlay: mvn install > 2) main: mvn package > 3) overlay web.xml is exists in final war if newer timestamp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2453) Site plugin NO locale
[ http://jira.codehaus.org/browse/MNG-2453?page=comments#action_72138 ] Vincent Siveton commented on MNG-2453: -- What is the difference with MNG-2418? Trygvis maybe? > Site plugin NO locale > - > > Key: MNG-2453 > URL: http://jira.codehaus.org/browse/MNG-2453 > Project: Maven 2 > Issue Type: Improvement > Components: Sites & Reporting > Environment: N/A >Reporter: David J. M. Karlsen >Priority: Minor > Attachments: site-plugin_no.properties > > > Norwegian (bokmål - NO_nb) translation. > I'll add "info" translation soon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2474) missing jar files in javax repository
[ http://jira.codehaus.org/browse/MNG-2474?page=all ] Vincent Siveton closed MNG-2474. Assignee: Vincent Siveton Resolution: Won't Fix Fix Version/s: 2.0.5 Sun's Binary License limitations. See: http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html > missing jar files in javax repository > - > > Key: MNG-2474 > URL: http://jira.codehaus.org/browse/MNG-2474 > Project: Maven 2 > Issue Type: Improvement > Components: Repositories >Affects Versions: 2.0.4 > Environment: independent >Reporter: Marcel Baumann > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > > Hi all > I do not know, who is responsible for the Raven 2 repository javax. There are > missing jar files in: > javax.transaction > javax.security > ...more? > Missing: > -- > 1) javax.transaction:jta:jar:1.0.1B > In the repository only these files exist: > http://www.ibiblio.org/maven2/javax/transaction/jta/1.0.1B/ > jta-1.0.1B.pom 08-Nov-2005 16:58 1k > jta-1.0.1B.pom.md5 08-Nov-2005 17:45 1k > jta-1.0.1B.pom.sha1 08-Nov-2005 17:45 1k > Thanks. > Marcel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-68) CLONE -Overlay war can overwrite main project web.xml
[ http://jira.codehaus.org/browse/MWAR-68?page=comments#action_72136 ] Stefan Seidel commented on MWAR-68: --- Bug still present in Maven 2.0.4. > CLONE -Overlay war can overwrite main project web.xml > - > > Key: MWAR-68 > URL: http://jira.codehaus.org/browse/MWAR-68 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.1 >Reporter: Stefan Seidel > Assigned To: Brett Porter > Fix For: 2.0.2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 1) overlay: mvn install > 2) main: mvn package > 3) overlay web.xml is exists in final war if newer timestamp -- 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: (MWAR-68) CLONE -Overlay war can overwrite main project web.xml
CLONE -Overlay war can overwrite main project web.xml - Key: MWAR-68 URL: http://jira.codehaus.org/browse/MWAR-68 Project: Maven 2.x War Plugin Issue Type: Bug Affects Versions: 2.0.1 Reporter: Stefan Seidel Assigned To: Brett Porter Fix For: 2.0.2 1) overlay: mvn install 2) main: mvn package 3) overlay web.xml is exists in final war if newer timestamp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2493) Snapshot plugin repositories should be included for reference at the Maven site
[ http://jira.codehaus.org/browse/MNG-2493?page=all ] Vincent Siveton closed MNG-2493. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.0.5 Applied with small changes (ie in agreement with http://docs.codehaus.org/display/MAVEN/Development+Procedures ) Thanks! > Snapshot plugin repositories should be included for reference at the Maven > site > --- > > Key: MNG-2493 > URL: http://jira.codehaus.org/browse/MNG-2493 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Reporter: Baerrach bonDierne > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > Attachments: MNG-2493-patch.txt > > > When developing a plugin (or patching an existing plugin), the plugin often > depends upon snapshot versions of plugins. > There is no reference material for where these snapshot plugin repositories > are located. > Luckily people respond on the list with this information, but it would help > to include it as part of the reference material on the web site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MASSEMBLY-104) fileMode doesn't work with Cygwin
[ http://jira.codehaus.org/browse/MASSEMBLY-104?page=all ] John Casey closed MASSEMBLY-104. Assignee: John Casey Resolution: Fixed Fix Version/s: 2.2 fixed in refactor. Two ITs - in the src/it/file-modes directory cover this. > fileMode doesn't work with Cygwin > - > > Key: MASSEMBLY-104 > URL: http://jira.codehaus.org/browse/MASSEMBLY-104 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Windows 2002 XP Pro running Cygwin >Reporter: Mark Heinze > Assigned To: John Casey > Fix For: 2.2 > > Attachments: assembly-bug.tar > > > The fileMode does not correctly set the permissions on the file. This happens > in the tag in the asssembly XML file. Any files > copied with this tag ends up with strange permissions (including those with > the default fileMode). -- 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: (WAGON-59) repository should have a flag to indicate whether it should be proxied
repository should have a flag to indicate whether it should be proxied -- Key: WAGON-59 URL: http://jira.codehaus.org/browse/WAGON-59 Project: wagon Issue Type: Improvement Reporter: Brett Porter as an improvement over relying on non-proxy-hosts, it should also be a configurable setting on a repository. It is likely this would be configurable all the way up to the POM in maven. -- 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: (MPA-80) Open a staging sites area at http://maven.zones.apache.org/staging/
Open a staging sites area at http://maven.zones.apache.org/staging/ --- Key: MPA-80 URL: http://jira.codehaus.org/browse/MPA-80 Project: Maven Project Administration Issue Type: Task Components: sites Affects Versions: 2006-q3 Reporter: Arnaud Heritier Assigned To: Jason van Zyl Priority: Minor As discussed here [1] it could be interesting for us to have a common staging area to deploy our documentations (instead of using our accounts on people.apache.org). Brett proposed to use the zone for that : http://maven.zones.apache.org/staging/ (maven 2) http://maven.zones.apache.org/staging/maven-1.x/ (maven 1 ie, following live site structure). I think that all committers must have the rights to deploy the web sites here. [1] http://www.nabble.com/CI-for-M1-%3A-Can-I-use-a-continuum-instance-somewhere---tf2051570.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: (MJAR-42) Add LICENCE and NOTICE files to the jar
[ http://jira.codehaus.org/browse/MJAR-42?page=comments#action_72130 ] Jochen Wiedmann commented on MJAR-42: - I'd like to recall that Maven is an Apache project. In other words, if there is something like "Apache-specific", then the "Maven standard" should at least make it possible to follow. Additionally, I'd like to point out a problem with Bretts suggestion to use the mechanism: If I do specify a resource, which lives in the base directory, then I'll encounter problems while building a source jar: The maven-source-plugin will include my whole project into the jar file. (This may be a bug in the maven-source-plugin, I am unsure what to think of it.) > Add LICENCE and NOTICE files to the jar > --- > > Key: MJAR-42 > URL: http://jira.codehaus.org/browse/MJAR-42 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Jeremy Boynes > Attachments: mvn-jar-patch.txt > > > Patch attached that adds project LICENSE and NOTICE files into the output > jar. By default it will add LICENSE.txt and NOTICE.txt files from the > project's basedir (if they are present) into the META-INF directory of the > 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] Commented: (MNG-1977) Global dependency exclusions
[ http://jira.codehaus.org/browse/MNG-1977?page=comments#action_72129 ] Gilles Tabary commented on MNG-1977: The squeakiest tire get the oil first : That would be indeed a much wanted feature. :-) Gilles Gilles Tabary > Global dependency exclusions > > > Key: MNG-1977 > URL: http://jira.codehaus.org/browse/MNG-1977 > Project: Maven 2 > Issue Type: New Feature > Components: POM >Reporter: Kees de Kooter > Fix For: 2.1 > > > I depend on some libraries, which in turn depend on something > (which in turn depend on something) that I don't want, because I declare > some other artifact in my pom.xml. > A concrete example: I don't want that the artifact "xerces" is imported in > my project because I declare to depend on "xercesImpl" which ships newer > libraries but with the same namespaces. > I guess I would need an "exclude transitive dependency at all", either > globally or from this and that artifact. I saw the tag, but it > forces me to be very verbose and have exact control on what is required by a > dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2494) Plugin development guide should have link to test harness plugin
[ http://jira.codehaus.org/browse/MNG-2494?page=all ] Vincent Siveton closed MNG-2494. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.0.5 Fixed in svn > Plugin development guide should have link to test harness plugin > > > Key: MNG-2494 > URL: http://jira.codehaus.org/browse/MNG-2494 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: Guides >Affects Versions: 2.0.4 >Reporter: Dave Syer > Assigned To: Vincent Siveton > Fix For: 2.0.5 > > > It's quite hard to find the URL for the test harness plugin > (http://maven.apache.org/shared/maven-plugin-testing-harness). Could someone > put a link in the main plugin API guide > (http://maven.apache.org/guides/plugin/guide-java-plugin-development.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] Closed: (MNG-2495) Javadocs for the test harness plugin would be very useful
[ http://jira.codehaus.org/browse/MNG-2495?page=all ] Vincent Siveton closed MNG-2495. Assignee: Vincent Siveton Resolution: Fixed Fixed in SVN. The site has been deployed. It should show up within the next 4 hours. > Javadocs for the test harness plugin would be very useful > - > > Key: MNG-2495 > URL: http://jira.codehaus.org/browse/MNG-2495 > Project: Maven 2 > Issue Type: Improvement > Components: Plugin API >Affects Versions: 2.0.4 >Reporter: Dave Syer > Assigned To: Vincent Siveton > > There is no javadoc report at > http://maven.apache.org/shared/maven-plugin-testing-harness. -- 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: (MWAR-67) webResource filtering needs filter
[ http://jira.codehaus.org/browse/MWAR-67?page=all ] Franz Allan Valencia See updated MWAR-67: - Attachment: MWAR-67-maven-war-plugin.patch Tomasz Pik, you can use MWAR-67-maven-war-plugin.patch in the mean time. This patch will allow you to use -D option without specifying a filter property file. However, this still lacks the neccessary test cases for that. i'm just going to submit another patch once i've finished the tests. > webResource filtering needs filter > -- > > Key: MWAR-67 > URL: http://jira.codehaus.org/browse/MWAR-67 > Project: Maven 2.x War Plugin > Issue Type: Bug >Reporter: Tomasz Pik >Priority: Minor > Attachments: MWAR-67-maven-war-plugin.patch > > > Filtering of webResources works only, if there's at least one > path/to/properties defined in pom. > So without such a configuration there's no possiblity to build war file with > filtering using values specified during build invocation, with -D options > (System properties are ignored). > Adding reference to (even empty) file using element 'solves' the > problem and properties defined using -D are used. -- 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: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts
[ http://jira.codehaus.org/browse/MWAR-58?page=all ] Marvin King updated MWAR-58: Assignee: (was: Marvin King) > consider the artifact classifier when checking for duplicated artifacts > --- > > Key: MWAR-58 > URL: http://jira.codehaus.org/browse/MWAR-58 > Project: Maven 2.x War Plugin > Issue Type: New Feature >Affects Versions: 2.1 >Reporter: Marvin King > Fix For: 2.0.2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > see > http://www.nabble.com/-m2--war-plugin%2C-ignores-classifier-in-dependency-tf1903970.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] Created: (MWAR-67) webResource filtering needs filter
webResource filtering needs filter -- Key: MWAR-67 URL: http://jira.codehaus.org/browse/MWAR-67 Project: Maven 2.x War Plugin Issue Type: Bug Reporter: Tomasz Pik Priority: Minor Filtering of webResources works only, if there's at least one path/to/properties defined in pom. So without such a configuration there's no possiblity to build war file with filtering using values specified during build invocation, with -D options (System properties are ignored). Adding reference to (even empty) file using element 'solves' the problem and properties defined using -D are used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-1977) Global dependency exclusions
[ http://jira.codehaus.org/browse/MNG-1977?page=comments#action_72122 ] Marc Portier commented on MNG-1977: --- Adding another possibly featured way to configure: * disable all transitive deps for certain scopes (e.g.: I'ld like transitive deps marked for 'runtime' and 'compile', but not for 'test') > Global dependency exclusions > > > Key: MNG-1977 > URL: http://jira.codehaus.org/browse/MNG-1977 > Project: Maven 2 > Issue Type: New Feature > Components: POM >Reporter: Kees de Kooter > Fix For: 2.1 > > > I depend on some libraries, which in turn depend on something > (which in turn depend on something) that I don't want, because I declare > some other artifact in my pom.xml. > A concrete example: I don't want that the artifact "xerces" is imported in > my project because I declare to depend on "xercesImpl" which ships newer > libraries but with the same namespaces. > I guess I would need an "exclude transitive dependency at all", either > globally or from this and that artifact. I saw the tag, but it > forces me to be very verbose and have exact control on what is required by a > dependency. -- 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-1042) Upload backport-util-concurrent 2.2 to ibiblio
Upload backport-util-concurrent 2.2 to ibiblio -- Key: MAVENUPLOAD-1042 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1042 Project: maven-upload-requests Issue Type: Task Reporter: Simone Bordet Currently, version 2.1 is uploaded to ibiblio. Just need to update the version in the pom and download the new jar. If it may help, it is already uploaded to the LiveTribe Maven2 repo (but that's not sync'ed with ibiblio): http://dist.codehaus.org/livetribe/maven/m2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2203) Problem with duplicates
[ http://jira.codehaus.org/browse/MNG-2203?page=all ] Maria Odea Ching updated MNG-2203: -- Due Date: 14/Aug/06 > Problem with duplicates > --- > > Key: MNG-2203 > URL: http://jira.codehaus.org/browse/MNG-2203 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.1, 2.0.3 > Environment: Windows XP SP 2 - JDK 1.5.06 - Maven 2.1-SNAPSHOT >Reporter: Francesco Tinti > Assigned To: Maria Odea Ching > Fix For: 2.0.5 > > Attachments: pomerr.zip > > Time Spent: 7 hours > Remaining Estimate: 20 hours > > Declare in POM a duplicate group-artifact dependency but with different > versions.: there's no log of duplicate entry. > Maven will also take care only of the latest dependency, so if the version is > ancient of the other, you can obtain (of course) compilation error. > In attachment a simple demonstration with a specific commons-io 1.2 function. -- 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-141) PDE singleton is put in MANIFEST.MF as a directive rather than an attribute. Error in Eclipse 3.1.2. Bundle-SymbolicName: cds_ss_applet;singleton:=true
[ http://jira.codehaus.org/browse/MECLIPSE-141?page=comments#action_72109 ] stephane bouchet commented on MECLIPSE-141: --- Hi, With Eclipse 3.2, you will not have this error. the "singleton:=true" does not make eclipse complaining.. Stéphane > PDE singleton is put in MANIFEST.MF as a directive rather than an attribute. > Error in Eclipse 3.1.2. Bundle-SymbolicName: cds_ss_applet;singleton:=true > --- > > Key: MECLIPSE-141 > URL: http://jira.codehaus.org/browse/MECLIPSE-141 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: PDE support >Affects Versions: 2.3 >Reporter: David Boden > > If the PDE plugin declares extension points, a directive is placed in the > MANIFEST.MF. It is of the form singleton:=true . This causes an error in > Eclipse. Unknown directive. > It should probably be a property of the form singleton=true (without the > colon ":" ) > I'll upgrade to Eclipse 3.2 to see if I still get the error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2489) New Maven-Shared-Jar - jar internals discovery component
[ http://jira.codehaus.org/browse/MNG-2489?page=all ] Emmanuel Venisse closed MNG-2489. - Resolution: Fixed I committed the one I have locally instead of the one attached because it didn't contains my changes about plexus components. I removed too the use of analyzers in Jar class because it isn't the best place to use them. If we want to populate classes and taxon fields, we need to use JarTaxonAnalyser.analyse and JarClassesAnalyszer.analyze before to call classes and taxon fields > New Maven-Shared-Jar - jar internals discovery component > > > Key: MNG-2489 > URL: http://jira.codehaus.org/browse/MNG-2489 > Project: Maven 2 > Issue Type: New Feature >Reporter: Joakim Erdfelt > Assigned To: Emmanuel Venisse > Attachments: MNG-2489-maven-shared-jar.tar.gz > > > Uploading a new maven-shared-jar component to allow for discovering the > internals of jar files. > * Packages. > * Class names. > * Imports. > * JDK Revision. > * Classes have Debug Enabled. > * File List. > * Taxonomy. > * Sealed Jar Indicator. > Useful for Maven Repository Manager and Maven Project Info Report. (patches > for those comming soon). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2495) Javadocs for the test harness plugin would be very useful
Javadocs for the test harness plugin would be very useful - Key: MNG-2495 URL: http://jira.codehaus.org/browse/MNG-2495 Project: Maven 2 Issue Type: Improvement Components: Plugin API Affects Versions: 2.0.4 Reporter: Dave Syer There is no javadoc report at http://maven.apache.org/shared/maven-plugin-testing-harness. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-2494) Plugin development guide should have link to test harness plugin
Plugin development guide should have link to test harness plugin Key: MNG-2494 URL: http://jira.codehaus.org/browse/MNG-2494 Project: Maven 2 Issue Type: Improvement Components: Documentation: Guides Affects Versions: 2.0.4 Reporter: Dave Syer It's quite hard to find the URL for the test harness plugin (http://maven.apache.org/shared/maven-plugin-testing-harness). Could someone put a link in the main plugin API guide (http://maven.apache.org/guides/plugin/guide-java-plugin-development.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] Updated: (MNG-2123) NullPointerException when a dependency uses version range and another uses an actual version incompatible with that range
[ http://jira.codehaus.org/browse/MNG-2123?page=all ] Edwin Punzalan updated MNG-2123: Attachment: MNG-2123-maven-artifact.patch I'm attaching the patch for this. I changed the default recommendation to RELEASE in case restrict does not find a valid version. Also changed the unit tests, since the tests show that null is expected which causes this bug. > NullPointerException when a dependency uses version range and another uses an > actual version incompatible with that range > - > > Key: MNG-2123 > URL: http://jira.codehaus.org/browse/MNG-2123 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.3, 2.0.2, 2.0.4 >Reporter: Carlos Sanchez > Assigned To: Edwin Punzalan > Fix For: 2.0.5 > > Attachments: MNG-2123-maven-artifact.patch, pom.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Struts 1.2.7 depends on commons-digester 1.6 and jasperreports 1.1.1 in [1.7,) > Build fails with a null pointer exception that is not very explanatory > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Unnamed - test:test:jar:1.0-SNAPSHOT > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for commons-digester:commons-digester > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > commons-digester:commons-digester > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:361) > at > org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:222) > at > org.apache.maven.artifact.resolver.ResolutionNode.getDependencyTrail(ResolutionNode.java:115) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:88) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1117) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:366) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: 1 second > [INFO] Finished at: Sun Mar 05 23:26:16 PST 2006 > [INFO] Final Memory: 3M/5M > [INFO] > ---
[jira] Created: (MRM-148) provide way of zipping the repository index for remote distribution
provide way of zipping the repository index for remote distribution --- Key: MRM-148 URL: http://jira.codehaus.org/browse/MRM-148 Project: Maven Repository Manager Issue Type: New Feature Reporter: Milos Kleint Attachments: archiver.patch for use in the IDEs, it would be nice to have the index for the remote repository readily available for download. the attached path solves that by always creating a zip file after the index is updated and placing it into the repository in .index folder. That way the IDE can easily check the location only with the knowledge of the repository url. -- 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
