[jira] Commented: (MNG-3333) range specified dependencies don't work
[ http://jira.codehaus.org/browse/MNG-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117708 ] Milos Kleint commented on MNG-: --- when was it fixed? the current computer is rather new, I got it a month ago, the local repository is completely new, so I'm wondering how come the metadata didn't get downloaded. > range specified dependencies don't work > --- > > Key: MNG- > URL: http://jira.codehaus.org/browse/MNG- > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.1 >Reporter: Milos Kleint >Priority: Blocker > Attachments: ranges.zip > > > current 2.1-SNAPSHOT > When a dependency is specified with version [1.0.4] the build of project > fails, so does project loading in the IDE. > Example project 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] Commented: (MNG-3278) classifiers in dependencyManagement don't work
[ http://jira.codehaus.org/browse/MNG-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117698 ] Andres Almiray commented on MNG-3278: - I too found this problem trying to configure TestNG in parent pom > classifiers in dependencyManagement don't work > -- > > Key: MNG-3278 > URL: http://jira.codehaus.org/browse/MNG-3278 > Project: Maven 2 > Issue Type: Bug >Reporter: Paul Sundling >Priority: Minor > > parent pom: > > > > > net.sf.json-lib > json-lib > 2.1 > jdk15 > > > > > If child pom will pick up everything else like excludes, except the > classifier, so classifier has to be added for every child pom. > > > > net.sf.json-lib > json-lib > jdk15 > > > > Expected to work, but fails: > > > > net.sf.json-lib > json-lib > > > -- 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-3333) range specified dependencies don't work
[ http://jira.codehaus.org/browse/MNG-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117694 ] Dennis Lundberg commented on MNG-: -- The metadata for commons-logging was incomplete. Several versions were missing. This is probably due to artifacts being converted from the Apache M1 repository. I fixed the metadata in the Apache M2 repo a while back. But Maven doesn't re-download files to the local repo, so you have to nuke that part of your local repo to get it working. > range specified dependencies don't work > --- > > Key: MNG- > URL: http://jira.codehaus.org/browse/MNG- > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.1 >Reporter: Milos Kleint >Priority: Blocker > Attachments: ranges.zip > > > current 2.1-SNAPSHOT > When a dependency is specified with version [1.0.4] the build of project > fails, so does project loading in the IDE. > Example project 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: (MANTLR-25) ClassCastException when calling mvn ant:ant
ClassCastException when calling mvn ant:ant --- Key: MANTLR-25 URL: http://jira.codehaus.org/browse/MANTLR-25 Project: Maven 2.x Antlr Plugin Issue Type: Bug Environment: java-config -L The following VMs are available for generation-2: 1) Blackdown JDK 1.4.2.03 [blackdown-jdk-1.4.2] 2) Sun 32bit JRE 1.6.0.03 [emul-linux-x86-java-1.6] *) Sun JDK 1.5.0.13 [sun-jdk-1.5] 4) Sun JDK 1.6.0.03 [sun-jdk-1.6] * Active vm emerge --info Portage 2.1.4_rc11 (default-linux/amd64/2006.1/desktop, gcc-4.2.2, glibc-2.7-r1, 2.6.23-gentoo x86_64) = System uname: 2.6.23-gentoo x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ Timestamp of tree: Unknown app-shells/bash: 3.2_p17-r1 dev-java/java-config: 1.3.7, 2.1.3 dev-lang/python: 2.5.1-r4 sys-apps/baselayout: 1.12.10-r5 sys-apps/sandbox:1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.23-r2 ACCEPT_KEYWORDS="amd64 ~amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="cvs distlocks metadata-transfer nostrip parallel-fetch sfperms strict unmerge-orphans userfetch userpriv usersandbox" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"; LANG="en_NZ" LC_ALL="en_NZ.utf8" LINGUAS="en en_GB en_NZ" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/home/alistair/gentoo/cvs/gentoo-x86" PORTDIR_OVERLAY="/home/alistair/gentoo/overlays/java-overlay /home/alistair/gentoo/overlays/java-experimental" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="X a52 aac acpi alsa amd64 apache2 berkdb bitmap-fonts cairo cdr clearcase cli cracklib crypt ctype cups cvs dbus doc dri dvd dvdr dvdread eds emboss encode esd fam firefox fortran gd gdbm gif glitz gpm gtk2 hal iconv ipv6 isdnlog java java5 javamail jpeg jpeg2k kde ldap lm_sensors mad midi mikmod mp3 mpeg mplayer mudflap mysql mysqli ncurses nls nptl nptlonly nsplugin offensive ogg opengl openmp pam pcre pdf perl png ppds pppd python qt3 qt4 quicktime readline reflection ruby sdl session source spell spl sql sqlite ssl subversion svg tcpd theora threads tiff tomcat truetype truetype-fonts type1-fonts unicode utempter vorbis xcomposite xine xml xorg xulrunner xv xvid xvmc zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_GB en_NZ" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS Reporter: Alistair Bush Attachments: mvnDebug.txt I received the following error when running mvn ant:ant on the openjpa project (http://openjpa.apache.org/). Still reproducible after removing ~/.m2 [INFO] [ERROR] FATAL ERROR [INFO] [INFO] java.util.HashMap [INFO] [DEBUG] Trace java.lang.ClassCastException:
[jira] Created: (MJAVADOC-163) excludePAckageNAmes don't work with antlr plugin
excludePAckageNAmes don't work with antlr plugin Key: MJAVADOC-163 URL: http://jira.codehaus.org/browse/MJAVADOC-163 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.3 Environment: maven 2.0.8 jdk 1.5.14 Reporter: Claudio D'Angelo Priority: Minor Attachments: pom.xml In my pom is configurated antlr plugin. When i start javadoc:javadoc the javadoc plugin documents all package althouh the excludePackageNames is configurated. If i comment the antlr plugin javadoc work correctly. In attachment my 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] Commented: (MNG-3333) range specified dependencies don't work
[ http://jira.codehaus.org/browse/MNG-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117684 ] Milos Kleint commented on MNG-: --- my local repository didn't include maven-metadata.xml files even though ti contained multiple versions of commons-logging. after deleting the whole directory in the local repository and downloading the bits from central, the metadate file appeared and the project stated building.. > range specified dependencies don't work > --- > > Key: MNG- > URL: http://jira.codehaus.org/browse/MNG- > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.1 >Reporter: Milos Kleint >Priority: Blocker > Attachments: ranges.zip > > > current 2.1-SNAPSHOT > When a dependency is specified with version [1.0.4] the build of project > fails, so does project loading in the IDE. > Example project 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: (MNG-3333) range specified dependencies don't work
range specified dependencies don't work --- Key: MNG- URL: http://jira.codehaus.org/browse/MNG- Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.1 Reporter: Milos Kleint Priority: Blocker Attachments: ranges.zip current 2.1-SNAPSHOT When a dependency is specified with version [1.0.4] the build of project fails, so does project loading in the IDE. Example project 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] Closed: (MNG-3332) Class-Path manifest entry should support maven repository layout
[ http://jira.codehaus.org/browse/MNG-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MNG-3332. - Resolution: Fixed fix in rev 605055. > Class-Path manifest entry should support maven repository layout > > > Key: MNG-3332 > URL: http://jira.codehaus.org/browse/MNG-3332 > Project: Maven 2 > Issue Type: Improvement > Components: maven-archiver >Affects Versions: Reviewed Pending Version Assignment >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: Reviewed Pending Version Assignment > > > The assembly plugin supports outputting all dependencies in a repository > layout. > The jar plugin should support adding the classpath manifest entry based on > the repository layout. > The combination of the two makes it easy to write a script to run the app: > "java -jar org/domain/project/projectApp.jar" at the base of the repository > layout. > Example of a Class-Path entry: > ClassPath: > org/springframework/spring-core/2.0/spring-core-2.0.jar;org/drools/drools-core/4.0/drools-core-4.0.jar;org/domain/project/projectApp.jar > Also see maven user mailing list "maven-jar-plugin: how to avoid conflicts in > " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MNG-3332) Class-Path manifest entry should support maven repository layout
[ http://jira.codehaus.org/browse/MNG-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy moved MJAR-94 to MNG-3332: --- Affects Version/s: (was: 2.1) Reviewed Pending Version Assignment Fix Version/s: (was: 2.2) Reviewed Pending Version Assignment Key: MNG-3332 (was: MJAR-94) Project: Maven 2 (was: Maven 2.x Jar Plugin) > Class-Path manifest entry should support maven repository layout > > > Key: MNG-3332 > URL: http://jira.codehaus.org/browse/MNG-3332 > Project: Maven 2 > Issue Type: Improvement > Components: maven-archiver >Affects Versions: Reviewed Pending Version Assignment >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: Reviewed Pending Version Assignment > > > The assembly plugin supports outputting all dependencies in a repository > layout. > The jar plugin should support adding the classpath manifest entry based on > the repository layout. > The combination of the two makes it easy to write a script to run the app: > "java -jar org/domain/project/projectApp.jar" at the base of the repository > layout. > Example of a Class-Path entry: > ClassPath: > org/springframework/spring-core/2.0/spring-core-2.0.jar;org/drools/drools-core/4.0/drools-core-4.0.jar;org/domain/project/projectApp.jar > Also see maven user mailing list "maven-jar-plugin: how to avoid conflicts in > " -- 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-3332) Class-Path manifest entry should support maven repository layout
[ http://jira.codehaus.org/browse/MNG-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-3332: -- Component/s: maven-archiver > Class-Path manifest entry should support maven repository layout > > > Key: MNG-3332 > URL: http://jira.codehaus.org/browse/MNG-3332 > Project: Maven 2 > Issue Type: Improvement > Components: maven-archiver >Affects Versions: Reviewed Pending Version Assignment >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: Reviewed Pending Version Assignment > > > The assembly plugin supports outputting all dependencies in a repository > layout. > The jar plugin should support adding the classpath manifest entry based on > the repository layout. > The combination of the two makes it easy to write a script to run the app: > "java -jar org/domain/project/projectApp.jar" at the base of the repository > layout. > Example of a Class-Path entry: > ClassPath: > org/springframework/spring-core/2.0/spring-core-2.0.jar;org/drools/drools-core/4.0/drools-core-4.0.jar;org/domain/project/projectApp.jar > Also see maven user mailing list "maven-jar-plugin: how to avoid conflicts in > " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAR-94) Class-Path manifest entry should support maven repository layout
Class-Path manifest entry should support maven repository layout Key: MJAR-94 URL: http://jira.codehaus.org/browse/MJAR-94 Project: Maven 2.x Jar Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.2 The assembly plugin supports outputting all dependencies in a repository layout. The jar plugin should support adding the classpath manifest entry based on the repository layout. The combination of the two makes it easy to write a script to run the app: "java -jar org/domain/project/projectApp.jar" at the base of the repository layout. Example of a Class-Path entry: ClassPath: org/springframework/spring-core/2.0/spring-core-2.0.jar;org/drools/drools-core/4.0/drools-core-4.0.jar;org/domain/project/projectApp.jar Also see maven user mailing list "maven-jar-plugin: how to avoid conflicts in " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MJAR-73) "mvn package" creates both lowercase "meta-inf" as well as uppercase "META-INF" directories
[ http://jira.codehaus.org/browse/MJAR-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MJAR-73: Fix Version/s: (was: 2.2) Removing Fix Version, because there was no fix for the issue. > "mvn package" creates both lowercase "meta-inf" as well as uppercase > "META-INF" directories > --- > > Key: MJAR-73 > URL: http://jira.codehaus.org/browse/MJAR-73 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Windows XP SP2 >Reporter: Ari Meyer >Assignee: Olivier Lamy > Attachments: maven-jar-bug.pdf > > > I am getting started with Maven 2.06, just trying to precisely follow the > BetterBuildsWithMaven.pdf instructions (2.6. Handling Classpath Resources). > I am running on Windows XP SP2. When I execute "mvn package" and open the > created JAR in Winzip, I see a "meta-inf" directory in addition to a > "META-INF" dir. Since I'm on a Win32 OS, when I extract the files, however, > I correctly see only the uppercase "META-INF" dir. I assume on an OS where > file/dir names are case-sensitive (such as UNIX variants), this could cause > problems (see bug MEAR-30). Even on Win32, it's definitely confusing, and > should be fixed. > I have attached a screen shot of what appears in WinZip. -- 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-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117661 ] Yuri Schimke commented on MNG-1412: --- Yes you are probably right, its mainly architectural issues i.e. patch jars. But fixing it would save so much trouble for so many people. So why argue so passionately about not fixing it, when its a simple fix. If you need a "good" reason to fix it, then It is bizarre that there is no predictable order for the classpath, even alphabetical would be better than quasi-random. > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > The .classpath file entries should be ordered by nearest transitiveness (if > that's a word). > For example, I have project A that depends on B that depends on C. The > classpath for A is generated in the order C, B. Ideally the classpath should > be in order of how near they are to the project, i.e. B, C. -- 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-3329) Improve the documentation concerning the archiver configuration
[ http://jira.codehaus.org/browse/MNG-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117660 ] Dennis Lundberg commented on MNG-3329: -- Examples are good, but I feel that they should explain concepts rather than details. Like the second example on the page you linked to. More of a "how do I" documentation than "what does this parameter do" documentation. I think that the details of the fields belong in a reference section, like we have for mojos http://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html or for the pom http://maven.apache.org/ref/current/maven-model/maven.html > Improve the documentation concerning the archiver configuration > --- > > Key: MNG-3329 > URL: http://jira.codehaus.org/browse/MNG-3329 > Project: Maven 2 > Issue Type: Improvement > Components: maven-archiver >Affects Versions: Shared Components >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: Reviewed Pending Version Assignment > > > Currently the documentation concerning the mavenArchiver configuration is > just a link to the javadoc. > We have to improve this with a sample configuration containing all options. -- 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
