[jira] Closed: (MAVENUPLOAD-1289) Please upload DWR 2.0.rc1 to maven repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1289?page=all ] Carlos Sanchez closed MAVENUPLOAD-1289. --- Assignee: Carlos Sanchez Resolution: Fixed Please upload DWR 2.0.rc1 to maven repo --- Key: MAVENUPLOAD-1289 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1289 Project: maven-upload-requests Issue Type: Task Reporter: Brendan Grainger Assigned To: Carlos Sanchez Attachments: dwr-2.0.rc1-bundle.jar DWR is already in the global Maven repository (see MAVENUPLOAD-433), this is the latest 2.0 rc1 version. I'm doing this, of course, with the agreement of Joe Walker, who is the author of DWR. I'm a commiter to the project at java.net. My handle is rainkinz. Regards, Brendan Grainger [EMAIL PROTECTED] -- 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-1297) XML Bind Builder [Ant]
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1297?page=comments#action_84176 ] Carlos Sanchez commented on MAVENUPLOAD-1297: - nothing can be removed from the central repo. If you want you may request new uploads. XML Bind Builder [Ant] -- Key: MAVENUPLOAD-1297 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1297 Project: maven-upload-requests Issue Type: Task Reporter: Seva Safris Assigned To: Carlos Sanchez The XML Bind solution is an alternative approach at XML binding for Java. The Generator solution is capable of generating source code from an XSD, allowing the Runtime to marshal and unmarshal those objects into XML. The builders are responsible for defining task and plugin classes for use of this solution with Ant and Maven. Builder-ant is for Ant, and Builder-maven is for 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] Closed: (MAVENUPLOAD-1299) Please help us upload the files from the JSON Tools project
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1299?page=all ] Carlos Sanchez closed MAVENUPLOAD-1299. --- Assignee: Carlos Sanchez Resolution: Fixed Please help us upload the files from the JSON Tools project --- Key: MAVENUPLOAD-1299 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1299 Project: maven-upload-requests Issue Type: Task Reporter: Changdong Li Assigned To: Carlos Sanchez Jsontools can 1.Parse JSON text files and convert these to a Java model. 2.Render a Java representation into text. 3. Serialize plain POJO clusters to a JSON representation. The goal is to provide a serializing mechanism which can cope with all kinds of Java datastructures (recursion, references, primitive types, ...) . 4. Map POJO to JSON, this time the JSON text should be as clean as possible. This tool is the best choice when data has to be communicated between Java and other programming languages who can parse JSON. 5. Validate the contents of a JSON file using a JSON schema. -- 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-1291) Upload ZK 2.2.0 to the central repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1291?page=all ] Carlos Sanchez closed MAVENUPLOAD-1291. --- Assignee: Carlos Sanchez Resolution: Fixed Upload ZK 2.2.0 to the central repository - Key: MAVENUPLOAD-1291 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1291 Project: maven-upload-requests Issue Type: Task Reporter: Tom M. Yeh Assigned To: Carlos Sanchez http://www.zkoss.org/maven/bundles/2.2.0/zcommon-2.2.0-bundle.jar http://www.zkoss.org/maven/bundles/2.2.0/zweb-2.2.0-bundle.jar http://www.zkoss.org/maven/bundles/2.2.0/zk-2.2.0-bundle.jar http://www.zkoss.org/maven/bundles/2.2.0/zul-2.2.0-bundle.jar http://www.zkoss.org/maven/bundles/2.2.0/zhtml-2.2.0-bundle.jar http://www.zkoss.org/maven/bundles/2.2.0/zkplus-2.2.0-bundle.jar http://www.zkoss.org/maven/bundles/2.2.0/dojoz-0.2.2-2-bundle.jar http://www.zkoss.org/maven/bundles/2.2.0/fckez-2.3-2-bundle.jar http://www.zkoss.org/maven/bundles/2.2.0/gmapsz-2.0-2-bundle.jar http://www.zkoss.org http://sourceforge.net/users/tomyeh/ ZK is an open-source Ajax Web framework that enables rich user interface for Web applications with no JavaScript and little programming. -- 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-1281) JFacets profile-based framework bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1281?page=all ] Carlos Sanchez closed MAVENUPLOAD-1281. --- Assignee: Carlos Sanchez Resolution: Fixed JFacets profile-based framework bundle -- Key: MAVENUPLOAD-1281 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1281 Project: maven-upload-requests Issue Type: Task Reporter: Remi VANKEISBELCK Assigned To: Carlos Sanchez http://jfacets.rvkb.com/pub/jfacets-1.3.6-bundle.jar http://jfacets.rvkb.com http://sf.net/projects/jfacets JFacets is a framework that allows to build profile-based applications easier, when you display and interact in a customized fashion with end-users based on their roles via facets. Upload please ! Thanks Remi - remi 'at' rvkb.com PS : It's my first maven repo upload, so apologies in advance if something isn't right in here ! -- 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-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=comments#action_84177 ] Carlos Sanchez commented on MAVENUPLOAD-1282: - poms are in the repo, can this issue be closed? PMD 3.9 bundle -- Key: MAVENUPLOAD-1282 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 Project: maven-upload-requests Issue Type: Task Reporter: Tom Copeland Assigned To: Carlos Sanchez PMD is a Java source code analyzer. It finds unused variables, empty catch blocks, unnecessary object creation, and so forth. -- 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-1287) Request to upload RCFaces jars
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1287?page=all ] Carlos Sanchez closed MAVENUPLOAD-1287. --- Assignee: Carlos Sanchez Resolution: Fixed Request to upload RCFaces jars -- Key: MAVENUPLOAD-1287 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1287 Project: maven-upload-requests Issue Type: Task Reporter: Fred Lefévère-Laoide Assigned To: Carlos Sanchez RC Faces or Rich Client Faces is a JavaServerFaces library that provides a component set for building next generation Web applications. RC Faces use AJAX technologies and an object-oriented JavaScript API to build highly dynamic pages. Ther's also another bundle to upload : http://rcfaces.org/maven/org.rcfaces.html-1.0Beta3-upload.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-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=comments#action_84178 ] Dennis Lundberg commented on MAVENUPLOAD-1282: -- The pom for pmd-3.9 seems to exist in the repo now, thanks. Unfortunately the pom refers to asm:asm:jar:3.0 that is not available in the repo. When I try to use the pom for this upload in the maven-pmd-plugin I get the following error. But I guess that is a different type of issue. Should I post this in MEV instead? If so this issue can be closed. Missing: -- 1) asm:asm:jar:3.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=asm -DartifactId=asm \ -Dversion=3.0 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.maven.plugins:maven-pmd-plugin:maven-plugin:2.2-SNAPSHOT 2) pmd:pmd:jar:3.9 3) asm:asm:jar:3.0 PMD 3.9 bundle -- Key: MAVENUPLOAD-1282 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 Project: maven-upload-requests Issue Type: Task Reporter: Tom Copeland Assigned To: Carlos Sanchez PMD is a Java source code analyzer. It finds unused variables, empty catch blocks, unnecessary object creation, and so forth. -- 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-1288) Request to upload RCFaces jars : html
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1288?page=all ] Carlos Sanchez closed MAVENUPLOAD-1288. --- Assignee: Carlos Sanchez Resolution: Fixed Request to upload RCFaces jars : html - Key: MAVENUPLOAD-1288 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1288 Project: maven-upload-requests Issue Type: Sub-task Reporter: Fred Lefévère-Laoide Assigned To: Carlos Sanchez RC Faces or Rich Client Faces is a JavaServerFaces library that provides a component set for building next generation Web applications. RC Faces use AJAX technologies and an object-oriented JavaScript API to build highly dynamic pages. linked to :http://rcfaces.org/maven/org.rcfaces.core-1.0Beta3-upload.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-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=comments#action_84179 ] Carlos Sanchez commented on MAVENUPLOAD-1282: - just attach or link a bundle for asm 3.0 PMD 3.9 bundle -- Key: MAVENUPLOAD-1282 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 Project: maven-upload-requests Issue Type: Task Reporter: Tom Copeland Assigned To: Carlos Sanchez PMD is a Java source code analyzer. It finds unused variables, empty catch blocks, unnecessary object creation, and so forth. -- 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-1301) JasperReports 1.3.0 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1301?page=all ] Carlos Sanchez closed MAVENUPLOAD-1301. --- Assignee: Carlos Sanchez Resolution: Fixed JasperReports 1.3.0 upload -- Key: MAVENUPLOAD-1301 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1301 Project: maven-upload-requests Issue Type: Task Reporter: Teodor Danciu Assigned To: Carlos Sanchez http://jasperreports.sourceforge.net/maven/jasperreports-1.3.0-bundle.jar http://sourceforge.net/projects/jasperreports http://sourceforge.net/project/memberlist.php?group_id=36382 Open Source Reporting Engine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1300) JasperReports 1.2.8 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1300?page=all ] Carlos Sanchez closed MAVENUPLOAD-1300. --- Assignee: Carlos Sanchez Resolution: Fixed JasperReports 1.2.8 upload -- Key: MAVENUPLOAD-1300 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1300 Project: maven-upload-requests Issue Type: Task Reporter: Teodor Danciu Assigned To: Carlos Sanchez http://jasperreports.sourceforge.net/maven/jasperreports-1.2.8-bundle.jar http://sourceforge.net/projects/jasperreports http://sourceforge.net/project/memberlist.php?group_id=36382 Open Source Reporting Engine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-1302) Please upload jMonit 0.1.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1302?page=all ] Carlos Sanchez closed MAVENUPLOAD-1302. --- Assignee: Carlos Sanchez Resolution: Fixed Please upload jMonit 0.1.0 -- Key: MAVENUPLOAD-1302 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1302 Project: maven-upload-requests Issue Type: Task Reporter: nicolas de loof Assigned To: Carlos Sanchez jMonit is a thin, performant, easy to use monitoring toolkit you can add to your app to monitor it's use on production server, including performances, load and scalability. -- 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-1303) pleas upload new version 1.0.1 of hivedoc-plugin
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1303?page=all ] Carlos Sanchez closed MAVENUPLOAD-1303. --- Assignee: Carlos Sanchez Resolution: Fixed pleas upload new version 1.0.1 of hivedoc-plugin Key: MAVENUPLOAD-1303 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1303 Project: maven-upload-requests Issue Type: Task Reporter: Marcus Schulte Assigned To: Carlos Sanchez -- 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: (MSITE-189) Coordinate the efforts of several users to write a Dashboard Plugin for Maven 2
[ http://jira.codehaus.org/browse/MSITE-189?page=comments#action_84180 ] Dennis Lundberg commented on MSITE-189: --- There was an announcement [1] on the user list for the Maven Author Plugin [2] which does something similar. [1] http://mail-archives.apache.org/mod_mbox/maven-users/200612.mbox/[EMAIL PROTECTED] [2] http://mvn-author-plug.sourceforge.net/ Coordinate the efforts of several users to write a Dashboard Plugin for Maven 2 --- Key: MSITE-189 URL: http://jira.codehaus.org/browse/MSITE-189 Project: Maven 2.x Site Plugin Issue Type: Task Reporter: Gisbert Amm Attachments: dashboard.zip, screenshot-1.jpg Coordinate the efforts of several users to write a Dashboard Plugin for Maven 2 Several people started their own Dashboard plugins (see http://jira.codehaus.org/browse/MSITE-188 and discussions on the users mailing list). It would be better, if one of those implementations would be adopted by the Maven team and the various development efforts would be coordinated and focused to that one. -- 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-182) site:stage doesn't bring over reports like javadoc
[ http://jira.codehaus.org/browse/MSITE-182?page=all ] Dennis Lundberg closed MSITE-182. - Resolution: Fixed Fix Version/s: 2.0 I have just tried this with a SVN trunk version of the site plugin and it is working for me. I tried using all these combinations: mvn site mvn site:stage mvn site:stage-deploy -DstagingSiteURL=file://... site:stage doesn't bring over reports like javadoc -- Key: MSITE-182 URL: http://jira.codehaus.org/browse/MSITE-182 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-5 Reporter: Brian Fox Fix For: 2.0 Perform site:stage with a report plugin like javadoc: reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId configuration minmemory128m/minmemory maxmemory512/maxmemory /configuration /plugin /plugins /reporting These reports are still generated in /target/site and not in the -DstagingDirectory= location. -- 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-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=comments#action_84184 ] Jeff Jensen commented on MAVENUPLOAD-1282: -- I've exchanged a few emails on the ASM list with Eugene Kuleshov of ASM on getting 3.0 to Ibiblio (he has done most/all of the prior upload requests). He mentioned that, on the last ASM upload request, he was told to begin deploying the ASM artifacts to their own repo, as it auto syncs with Ibiblio. He is starting to work on that, but I am not sure of his timeline yet. I asked him if he would mind commenting on this issue to let us know. http://www.objectweb.org/wws/arc/asm/2007-01/msg1.html PMD 3.9 bundle -- Key: MAVENUPLOAD-1282 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 Project: maven-upload-requests Issue Type: Task Reporter: Tom Copeland Assigned To: Carlos Sanchez PMD is a Java source code analyzer. It finds unused variables, empty catch blocks, unnecessary object creation, and so forth. -- 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: (MPPMD-29) Upgrade to PMD 3.9
[ http://jira.codehaus.org/browse/MPPMD-29?page=comments#action_84185 ] Jeff Jensen commented on MPPMD-29: -- Waiting for arrival of ASM 3.0 on Ibiblio (that is a work in progress). Upgrade to PMD 3.9 -- Key: MPPMD-29 URL: http://jira.codehaus.org/browse/MPPMD-29 Project: maven-pmd-plugin Issue Type: Task Affects Versions: 1.9 Reporter: Anthony Whitford Assigned To: Jeff Jensen Fix For: 1.10 PMD 3.8 was released October 4, 2006. The Maven plugin should be updated too. http://sourceforge.net/project/shownotes.php?release_id=452776group_id=56262 -- 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: (MSITE-189) Coordinate the efforts of several users to write a Dashboard Plugin for Maven 2
[ http://jira.codehaus.org/browse/MSITE-189?page=comments#action_84188 ] Dennis Lundberg commented on MSITE-189: --- My bad. I thought with the mvn moniker in the name that it was an M2 plugin for sure. Coordinate the efforts of several users to write a Dashboard Plugin for Maven 2 --- Key: MSITE-189 URL: http://jira.codehaus.org/browse/MSITE-189 Project: Maven 2.x Site Plugin Issue Type: Task Reporter: Gisbert Amm Attachments: dashboard.zip, screenshot-1.jpg Coordinate the efforts of several users to write a Dashboard Plugin for Maven 2 Several people started their own Dashboard plugins (see http://jira.codehaus.org/browse/MSITE-188 and discussions on the users mailing list). It would be better, if one of those implementations would be adopted by the Maven team and the various development efforts would be coordinated and focused to that one. -- 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: (MPMD-41) Upgrade to PMD 3.8
[ http://jira.codehaus.org/browse/MPMD-41?page=comments#action_84189 ] Dennis Lundberg commented on MPMD-41: - We also need the pmd dependency asm 3.0 to be uploaded in the repo in one way or the other. See also http://www.objectweb.org/wws/arc/asm/2007-01/msg1.html Upgrade to PMD 3.8 -- Key: MPMD-41 URL: http://jira.codehaus.org/browse/MPMD-41 Project: Maven 2.x Pmd Plugin Issue Type: Task Affects Versions: 2.1 Reporter: Anthony Whitford Assigned To: Dennis Lundberg PMD 3.8 was released October 4, 2006. The Maven plugin should be updated too. http://sourceforge.net/project/shownotes.php?release_id=452776group_id=56262 -- 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-2743) Dependency poms not timely merged with parents
Dependency poms not timely merged with parents
--
Key: MNG-2743
URL: http://jira.codehaus.org/browse/MNG-2743
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.4
Reporter: Kenney Westerhof
Priority: Blocker
POM's of dependencies are not properly merged with their parents.
It could be that they're not merged at all, or only partly. Since the code to
merge poms is the same
everywhere, and repository tags are merged for local poms, I fear that
they're not merged at all.
With this setup:
* local workspace:
** project A
*** depends on remote artifact B, residing in 'central'
* repository central:
** artifact B (cocoon-core)
*** has parent P (cocoon), also here at central
*** declares a dependency on D, residing in repo R (not a standard repository)
** pom P, declares repository R
* repository R:
** artifact D (avalon-framework-impl)
*** declares dependency on lib L, also here at repository R
** artifact L (avalon-framework-api)
When running mvn install on local project A, observe the following log:
{nopaste}
// cocoon-core has been resolved, now it's dependency poms are resolved:
[DEBUG] Trying repository central
Downloading:
http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[DEBUG] Artifact not found - using stub model: Unable to download the artifact
from any repository
org.apache.avalon.framework:avalon-framework-impl:pom:4.3
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[DEBUG] Using defaults for missing POM
org.apache.avalon.framework:avalon-framework-impl:pom:4.3:compile
// note: above, the parent of cocoon-core (B) (which is cocoon (P)), is not
merged, as the repo R is not
// visible in B to resolve D
// now, the artifacts themselves are downloaded
[DEBUG] Trying repository central
Downloading:
http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
// Here, repo R _is_ used to search, which means that the parent P is merged
with B and the repo is available
[DEBUG] Trying repository apache.snapshot
Downloading:
http://people.apache.org/maven-snapshot-repository/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework
-impl-4.3.jar
2/56K^M3/56K^M7/56K^M8/56K^M9/56K^M13/56K^M17/56K^M19/56K^M20/56K^M24/56K^M28/56K^M32/56K^M36/56K^M40/56K^M42/56K^M43/56K^M44/56K^M46/
56K^M47/56K^M49/56K^M50/56K^M52/56K^M53/56K^M54/56K^M56/56K^M56K downloaded
[DEBUG] Artifact resolved
{nopaste}
The problem here is that the jar is now available in the local repo, but the
pom is not, and the dependencies of D aren't downloaded.
It seems pom B is only merged with P _after_ all dependency poms for B have
been resolved.
--
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-2743) Dependency poms not timely merged with parents
[ http://jira.codehaus.org/browse/MNG-2743?page=all ]
Kenney Westerhof updated MNG-2743:
--
Description:
POM's of dependencies are not properly merged with their parents.
It could be that they're not merged at all, or only partly. Since the code to
merge poms is the same
everywhere, and repository tags are merged for local poms, I fear that
they're not merged at all.
With this setup:
* local workspace:
** project A
*** depends on remote artifact B, residing in 'central'
* repository central:
** artifact B (cocoon-core)
*** has parent P (cocoon), also here at central
*** declares a dependency on D, residing in repo R (not a standard repository)
** pom P, declares repository R
* repository R:
** artifact D (avalon-framework-impl)
*** declares dependency on lib L, also here at repository R
** artifact L (avalon-framework-api)
When running mvn install on local project A, observe the following log:
{noformat}
// cocoon-core has been resolved, now it's dependency poms are resolved:
[DEBUG] Trying repository central
Downloading:
http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[DEBUG] Artifact not found - using stub model: Unable to download the artifact
from any repository
org.apache.avalon.framework:avalon-framework-impl:pom:4.3
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[DEBUG] Using defaults for missing POM
org.apache.avalon.framework:avalon-framework-impl:pom:4.3:compile
// note: above, the parent of cocoon-core (B) (which is cocoon (P)), is not
merged, as the repo R is not
// visible in B to resolve D
// now, the artifacts themselves are downloaded
[DEBUG] Trying repository central
Downloading:
http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
// Here, repo R _is_ used to search, which means that the parent P is merged
with B and the repo is available
[DEBUG] Trying repository apache.snapshot
Downloading:
http://people.apache.org/maven-snapshot-repository/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework
-impl-4.3.jar
2/56K^M3/56K^M7/56K^M8/56K^M9/56K^M13/56K^M17/56K^M19/56K^M20/56K^M24/56K^M28/56K^M32/56K^M36/56K^M40/56K^M42/56K^M43/56K^M44/56K^M46/
56K^M47/56K^M49/56K^M50/56K^M52/56K^M53/56K^M54/56K^M56/56K^M56K downloaded
[DEBUG] Artifact resolved
{noformat}
The problem here is that the jar is now available in the local repo, but the
pom is not, and the dependencies of D aren't downloaded.
It seems pom B is only merged with P _after_ all dependency poms for B have
been resolved.
was:
POM's of dependencies are not properly merged with their parents.
It could be that they're not merged at all, or only partly. Since the code to
merge poms is the same
everywhere, and repository tags are merged for local poms, I fear that
they're not merged at all.
With this setup:
* local workspace:
** project A
*** depends on remote artifact B, residing in 'central'
* repository central:
** artifact B (cocoon-core)
*** has parent P (cocoon), also here at central
*** declares a dependency on D, residing in repo R (not a standard repository)
** pom P, declares repository R
* repository R:
** artifact D (avalon-framework-impl)
*** declares dependency on lib L, also here at repository R
** artifact L (avalon-framework-api)
When running mvn install on local project A, observe the following log:
{nopaste}
// cocoon-core has been resolved, now it's dependency poms are resolved:
[DEBUG] Trying repository central
Downloading:
http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.pom
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[DEBUG] Artifact not found - using stub model: Unable to download the artifact
from any repository
org.apache.avalon.framework:avalon-framework-impl:pom:4.3
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[DEBUG] Using defaults for missing POM
org.apache.avalon.framework:avalon-framework-impl:pom:4.3:compile
// note: above, the parent of cocoon-core (B) (which is cocoon (P)), is not
merged, as the repo R is not
// visible in B to resolve D
// now, the artifacts themselves are downloaded
[DEBUG] Trying repository central
Downloading:
http://repo1.maven.org/maven2/org/apache/avalon/framework/avalon-framework-impl/4.3/avalon-framework-impl-4.3.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
// Here, repo R _is_ used to search, which means that the parent P is merged
with B and the repo is available
[DEBUG] Trying repository apache.snapshot
[jira] Commented: (MAVENUPLOAD-1282) PMD 3.9 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1282?page=comments#action_84195 ] Eugene Kuleshov commented on MAVENUPLOAD-1282: -- Still waiting response from OW folks. PMD 3.9 bundle -- Key: MAVENUPLOAD-1282 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1282 Project: maven-upload-requests Issue Type: Task Reporter: Tom Copeland Assigned To: Carlos Sanchez PMD is a Java source code analyzer. It finds unused variables, empty catch blocks, unnecessary object creation, and so forth. -- 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-2744) checksum comparison should be case-insensitive
checksum comparison should be case-insensitive -- Key: MNG-2744 URL: http://jira.codehaus.org/browse/MNG-2744 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.4 Reporter: Ian Springer Validation of MD5 and SHA1 checksums should be case-insensitive (since the individual characters represent hexadecimal digits). For example: [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '9657ed010cea89caa1e35ae326dfccf28ea007f5'; remote = '9657ED010CEA89CAA1E35AE326DFCCF28EA007F5' - RETRYING -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-90) siternderer does not build
siternderer does not build -- Key: DOXIA-90 URL: http://jira.codehaus.org/browse/DOXIA-90 Project: doxia Issue Type: Bug Components: Site Renderer Reporter: Henning Schmiedehausen Fix For: 1.0 Attachments: ds.patch The doxia-siterenderer module does not build. it does some automatic dependency resolution for commons-collections and ends up with version 2.0 which does not contain a required class: patch is attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPIR-60) Current head throws NPE when generating reports
Current head throws NPE when generating reports --- Key: MPIR-60 URL: http://jira.codehaus.org/browse/MPIR-60 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Reporter: Henning Schmiedehausen Fix For: 2.1 The current head of this plugin does not generate the reports but throws NPEs: java.lang.NullPointerException at org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:141) at org.codehaus.plexus.i18n.DefaultI18N.getString(DefaultI18N.java:206) at org.apache.maven.report.projectinfo.LicenseReport.getName(LicenseReport.java:75) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:122) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:260) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:116) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:127) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:95) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:418) 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:327) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:120) at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) 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) -- 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: (SUREFIRE-31) support junit 4.0
[ http://jira.codehaus.org/browse/SUREFIRE-31?page=all ] Tom Huybrechts updated SUREFIRE-31: --- Attachment: surefire-junit4.patch previous patch was missing a pom... support junit 4.0 - Key: SUREFIRE-31 URL: http://jira.codehaus.org/browse/SUREFIRE-31 Project: surefire Issue Type: Improvement Components: Junit 4.x support Reporter: John Didion Fix For: 2.1 Attachments: SUREFIRE-31-maven-surefire-plugin.patch, SUREFIRE-31-surefire-trunk.patch, surefire-junit4.patch, surefire-junit4.patch, surefire-junit4.zip, SUREFIRE31_karl_maven-surefire-plugin.patch, SUREFIRE31_karl_surefire_surefire-providers_surefire-junit.patch, SUREFIRE31_karl_surefire_surefire-providers_surefire-junit_2ndMethod.patch I know this is a pretty sizable task. I just wanted to get it in the system now that 4.0 has officially been released. Hopefully this will generate some discussion about how 4.0 will be handled - mainly if it will require a completely seperate implemenation of surefire (keeping the same API so it can easily be used by the maven plugin), or if use of 4.0 will be made a configurable option of the current surefire. Here's some additional features I'd like to see: 1. Ability to categorize tests. Unfortunately, 4.0 doesn't include an @Category annotation, or make category a parameter of @Test. However, the filtering mechanism provided by 4.0 is sufficent to support categories given the presense of such an annotation. I recommend putting the @Category annotation in a seperate module (surefire-annotations?) and build support for it into surefire. Hopefully the junit guys could be convinced to incorporate it in a later version. 2. Similarly, support repeated tests via an @Repeated annotation. I'm not sure how easy this would be to do external to junit. -- 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: (SUREFIRE-31) support junit 4.0
[ http://jira.codehaus.org/browse/SUREFIRE-31?page=all ] Jason van Zyl closed SUREFIRE-31. - Resolution: Fixed Patches applied. Final form taken from Tom. Thanks. support junit 4.0 - Key: SUREFIRE-31 URL: http://jira.codehaus.org/browse/SUREFIRE-31 Project: surefire Issue Type: Improvement Components: Junit 4.x support Reporter: John Didion Assigned To: Jason van Zyl Fix For: 2.1 Attachments: SUREFIRE-31-maven-surefire-plugin.patch, SUREFIRE-31-surefire-trunk.patch, surefire-junit4.patch, surefire-junit4.patch, surefire-junit4.zip, SUREFIRE31_karl_maven-surefire-plugin.patch, SUREFIRE31_karl_surefire_surefire-providers_surefire-junit.patch, SUREFIRE31_karl_surefire_surefire-providers_surefire-junit_2ndMethod.patch I know this is a pretty sizable task. I just wanted to get it in the system now that 4.0 has officially been released. Hopefully this will generate some discussion about how 4.0 will be handled - mainly if it will require a completely seperate implemenation of surefire (keeping the same API so it can easily be used by the maven plugin), or if use of 4.0 will be made a configurable option of the current surefire. Here's some additional features I'd like to see: 1. Ability to categorize tests. Unfortunately, 4.0 doesn't include an @Category annotation, or make category a parameter of @Test. However, the filtering mechanism provided by 4.0 is sufficent to support categories given the presense of such an annotation. I recommend putting the @Category annotation in a seperate module (surefire-annotations?) and build support for it into surefire. Hopefully the junit guys could be convinced to incorporate it in a later version. 2. Similarly, support repeated tests via an @Repeated annotation. I'm not sure how easy this would be to do external to junit. -- 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-2694) property in plugin dependency's systemPath is not resolved and causes system-scoped dependency must specify an absolute path systemPath.
[ http://jira.codehaus.org/browse/MNG-2694?page=comments#action_84205 ]
Ian Springer commented on MNG-2694:
---
The same problem exists for system dependencies defined in a non-plugin
pom.xml.
Would someone please provide a fix for this? It's preventing me from doing what
I need to do in my build, and I don't see any workarounds to the bug.
property in plugin dependency's systemPath is not resolved and causes
system-scoped dependency must specify an absolute path systemPath.
--
Key: MNG-2694
URL: http://jira.codehaus.org/browse/MNG-2694
Project: Maven 2
Issue Type: Bug
Components: Bootstrap Build
Affects Versions: 2.0.4
Reporter: Willie Vu
In a plugin pom.xml,
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version[9.0,)/version
scopesystem/scope
systemPath${wl.home}/server/lib/weblogic.jar/systemPath
/dependency
In ~/.m2/setting.xml,
settings
profiles
profile
idweblogicConfig/id
activation
activeByDefault/
/activation
properties
wl.homec:/java/bea-9.2/weblogic92/wl.home
/properties
/profile
/profiles
activeProfiles
activeProfileweblogicConfig/activeProfile
/activeProfiles
/settings
When build the plugin, it works fine.
In a project that uses this plugin, when build, it causes the following error:
Project ID: org.codehaus.mojo:weblogic-maven-plugin
POM Location: Artifact
[org.codehaus.mojo:weblogic-maven-plugin:pom:2.9.0-SNAPSHOT]
Validation Messages:
[0] For dependency Dependency {groupId=weblogic, artifactId=weblogic,
version=[9.0,), type=jar}: system-scoped dependency must specify an absolute
path systemPath.
--
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: (MAVENUPLOAD-1304) org.springframework:beandoc:0.7.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1304?page=all ] fabrizio giustina updated MAVENUPLOAD-1304: --- Project URL: http://opensource.atlassian.com/confluence/spring/display/BDOC/Home (was: http://openutils.sourceforge.net/m2bundles/beandoc-0.7.1-bundle.jar) org.springframework:beandoc:0.7.1 - Key: MAVENUPLOAD-1304 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1304 Project: maven-upload-requests Issue Type: Task Reporter: fabrizio giustina -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MREPOSITORY-6) Don't check for License.txt file, but verify the licenses element in pom.xml
[ http://jira.codehaus.org/browse/MREPOSITORY-6?page=all ] fabrizio giustina closed MREPOSITORY-6. --- Assignee: fabrizio giustina Resolution: Fixed Fix Version/s: 2.1 fixed in svn Don't check for License.txt file, but verify the licenses element in pom.xml Key: MREPOSITORY-6 URL: http://jira.codehaus.org/browse/MREPOSITORY-6 Project: Maven 2.x Repository Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: fabrizio giustina Assigned To: fabrizio giustina Fix For: 2.1 repository:bundle-create checks for the existence of a License.txt file, that was only uploaded in maven 1 repositories. It should instead check for the licenses element in pom.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] Closed: (MREPOSITORY-2) project.scm.connection should not be required for bundle-create
[ http://jira.codehaus.org/browse/MREPOSITORY-2?page=all ] fabrizio giustina closed MREPOSITORY-2. --- Assignee: fabrizio giustina Resolution: Fixed Fix Version/s: 2.1 I agree, limitation removed for version 2.1 project.scm.connection should not be required for bundle-create --- Key: MREPOSITORY-2 URL: http://jira.codehaus.org/browse/MREPOSITORY-2 Project: Maven 2.x Repository Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Wendy Smoak Assigned To: fabrizio giustina Fix For: 2.1 It is not possible to create an upload bundle without specifying project/scm/connection. Some projects are not under source control, or the source may not be accessible by the public, so this element should not be required. To reproduce: $ mvn archetype:create -DartifactId=test -DgroupId=com.example $ cd test $ mvn repository:bundle-create ... [INFO] [repository:bundle-create] [INFO] - [ERROR] BUILD ERROR [INFO] - [INFO] Project scm element is null. [INFO] - After adding scm/url to pom.xml: $ mvn repository:bundle-create ... [INFO] [repository:bundle-create] [INFO] -- [ERROR] BUILD ERROR [INFO] -- [INFO] project.scm.connection must be present. [INFO] -- -- 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-419) Can't click to see the latest build results from the main page
[ http://jira.codehaus.org/browse/CONTINUUM-419?page=comments#action_84210 ] Wendy Smoak commented on CONTINUUM-419: --- This seems to be resolved. From the Project Group Summary page, you can click on the icon in the first column (success, error, failure, in progress) and see the build results. If the build is in progress, you can refresh the build results page to update the build output text. (See CONTINUUM-614 for a request to auto-refresh the build results page.) Can't click to see the latest build results from the main page -- Key: CONTINUUM-419 URL: http://jira.codehaus.org/browse/CONTINUUM-419 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.0 Reporter: David Blevins Assigned To: Emmanuel Venisse Priority: Trivial Fix For: 1.1 When you are at the projects page (Summary.vm/fid/continuumProject) it's really annoying you can't just click somewhere and see the latest build results. You have to click Build History then the top results item, which is a big of traveling. -- 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: (MAVENUPLOAD-1280) jMimeMagic 0.1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1280?page=all ] David Castro updated MAVENUPLOAD-1280: -- Attachment: jmimemagic-0.1.1-bundle.jar new bundle jar created with artifact:create-upload-bundl jMimeMagic 0.1.1 -- Key: MAVENUPLOAD-1280 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1280 Project: maven-upload-requests Issue Type: Task Reporter: David Castro Assigned To: Carlos Sanchez Attachments: jmimemagic-0.1.1-bundle.jar jMimeMagic is a Java library for determining the content type of files or streams. -- 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
