[jira] Commented: (MAVENUPLOAD-1503) Please upload DWR 2.0.1 to maven repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94303 ] Brendan Grainger commented on MAVENUPLOAD-1503: --- Sorry, bundle url should be: https://dwr.dev.java.net/files/documents/2427/56799/dwr-2.0.1-bundle.jar and Project URL is: http://getahead.org/dwr Regards Brendan (I really shouldn't be doing this at 4 in the morning) > Please upload DWR 2.0.1 to maven repo > - > > Key: MAVENUPLOAD-1503 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1503 > Project: maven-upload-requests > Issue Type: Task >Reporter: Brendan Grainger > Attachments: dwr-2.0.1-bundle.jar > > > DWR is already in the global Maven repository (see MAVENUPLOAD-1318), this is > the latest 2.0.1 version. > I've attached the bundle and it is also available on the project page at > java.net. Please let me know if there are any issues. > 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] Created: (MAVENUPLOAD-1503) Please upload DWR 2.0.1 to maven repo
Please upload DWR 2.0.1 to maven repo - Key: MAVENUPLOAD-1503 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1503 Project: maven-upload-requests Issue Type: Task Reporter: Brendan Grainger Attachments: dwr-2.0.1-bundle.jar DWR is already in the global Maven repository (see MAVENUPLOAD-1318), this is the latest 2.0.1 version. I've attached the bundle and it is also available on the project page at java.net. Please let me know if there are any issues. 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] Created: (MNG-2965) Update svn:ignores for developing with eclipse
Update svn:ignores for developing with eclipse
--
Key: MNG-2965
URL: http://jira.codehaus.org/browse/MNG-2965
Project: Maven 2
Issue Type: Improvement
Components: Bootstrap & Build
Affects Versions: 2.0.7
Reporter: Mark Hobson
Need to add the following to their respective svn:ignore properties:
{noformat}
? maven-artifact-manager\.settings
? maven-artifact-test\.settings
? maven-artifact\.settings
? maven-core\.settings
? maven-error-diagnostics\.settings
? maven-model\.settings
? maven-monitor\.settings
? maven-plugin-api\.settings
? maven-plugin-descriptor\.settings
? maven-plugin-parameter-documenter\.settings
? maven-plugin-registry\.settings
? maven-profile\.settings
? maven-project\.settings
? maven-reporting\maven-reporting-api\.settings
? maven-repository-metadata\.settings
? maven-script\maven-script-ant\.classpath
? maven-script\maven-script-ant\.project
? maven-script\maven-script-ant\.settings
? maven-script\maven-script-beanshell\.settings
? maven-settings\.settings
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1256) Email address is missing from the Project Group 'Members' tab
Email address is missing from the Project Group 'Members' tab - Key: CONTINUUM-1256 URL: http://jira.codehaus.org/browse/CONTINUUM-1256 Project: Continuum Issue Type: Improvement Reporter: Teodoro Cue Jr. Priority: Minor The Project Group 'Members' tab allows the user to search by email address, but the email address is not displayed on the page. There should be a column for email address. -- 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: (CONTINUUM-1256) Email address is missing from the Project Group 'Members' tab
[ http://jira.codehaus.org/browse/CONTINUUM-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated CONTINUUM-1256: --- Component/s: Web - UI > Email address is missing from the Project Group 'Members' tab > - > > Key: CONTINUUM-1256 > URL: http://jira.codehaus.org/browse/CONTINUUM-1256 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Reporter: Teodoro Cue Jr. >Priority: Minor > Attachments: CONTINUUM-1256-continuum-webapp.patch > > > The Project Group 'Members' tab allows the user to search by email address, > but the email address is not displayed on the page. > There should be a column for email address. -- 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-2966) Get optional transitive dependencies
Get optional transitive dependencies
Key: MNG-2966
URL: http://jira.codehaus.org/browse/MNG-2966
Project: Maven 2
Issue Type: Improvement
Components: Dependencies
Reporter: Daniel Beland
I would like to be able to add an includes statement on a dependency to get its
optional dependency(ies).
ie:
hibernate
hibernate
3.2.1.ga
jgroups
jgroups-all
runtime
false
For example, I use hibernate 3.2.1.ga, it has an optional dependency on
jgroups-all-2.2.8.
I would like to be able to add an inclusion statement on the hibernate lib to
tell that I want to include jgroups as well.
The main reason for this is that I want the same version as specified in the
hibernate pom.
This way, upgrading hibernate would also upgrade my version of jgroups at the
same time.
Obviously, we need to be able to define a scope and optional attribute as well
(not inherited)
Or maybe we could set the dependency explicitly in the pom without specifying
the version and have maven resolve the version from the nearest source (as it
does normally) automatically or we specify where to resolve it.
ie something like:
jgroups
jgroups-all
hibernate
hibernate
${hibernate.version}
runtime
false
--
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: (CONTINUUM-1256) Email address is missing from the Project Group 'Members' tab
[ http://jira.codehaus.org/browse/CONTINUUM-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teodoro Cue Jr. updated CONTINUUM-1256: --- Attachment: CONTINUUM-1256-continuum-webapp.patch Patch attached. > Email address is missing from the Project Group 'Members' tab > - > > Key: CONTINUUM-1256 > URL: http://jira.codehaus.org/browse/CONTINUUM-1256 > Project: Continuum > Issue Type: Improvement > Components: Web - UI >Reporter: Teodoro Cue Jr. >Assignee: Teodoro Cue Jr. >Priority: Minor > Attachments: CONTINUUM-1256-continuum-webapp.patch > > > The Project Group 'Members' tab allows the user to search by email address, > but the email address is not displayed on the page. > There should be a column for email address. -- 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: (MRELEASE-226) Provide an option to create a branch for maintenance releases
[ http://jira.codehaus.org/browse/MRELEASE-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94307 ] Emmanuel Venisse commented on MRELEASE-226: --- 1 and 2 can be implemented (and must be). We'll can update all versions (without manual update) in the plugin as we have all the code for that in the release plugin. > Provide an option to create a branch for maintenance releases > - > > Key: MRELEASE-226 > URL: http://jira.codehaus.org/browse/MRELEASE-226 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Environment: All >Reporter: Jim Crossley > > This email thread prompted this issue: http://www.mail-archive.com/[EMAIL > PROTECTED]/msg65485.html > As I [Heinrich Nirschl] see it there are two solutions: > 1) starting the maintenance branch before the release and doing the > release on the branch, in this case you have to manually adjust the > version on the trunk. > 2) doing the release on the trunk and starting the maintenance branch > from the tagged version, in this case the version has to be manually > updated on the branch. > Both approaches work, but there is some manual version editing in > both. Once the branching is done, the release plugin works fine on the > branch (for releasing further maintenance releases) and on the trunk > (for releasing the next major release). The manual update is only > necessary once per branch. -- 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-82) wagon-webdav does not set http-proxy correctly
wagon-webdav does not set http-proxy correctly -- Key: WAGON-82 URL: http://jira.codehaus.org/browse/WAGON-82 Project: wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 1.0-beta-2 Environment: any system Reporter: Marc Wilhelm Priority: Blocker Webdav connections through a http-proxy are currently not possible. The webdav provider opens first a connection to the target system and checks after this, if a proxy should be used. To fix this in the method "org.apache.maven.wagon.providers.webdav.WebdavWagon#openConnection()" the call "webdavResource = new CorrectedWebdavResource( httpURL );" must be changed into "webdavResource = new CorrectedWebdavResource( );" and after configuring the http-proxy the method call "webdavResource.setHttpURL(httpURL);" must be added. -- 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-82) wagon-webdav does not set http-proxy correctly
[ http://jira.codehaus.org/browse/WAGON-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94317 ] Emmanuel Venisse commented on WAGON-82: --- can you provide a patch instead of explain how to do it? Thanks. > wagon-webdav does not set http-proxy correctly > -- > > Key: WAGON-82 > URL: http://jira.codehaus.org/browse/WAGON-82 > Project: wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 1.0-beta-2 > Environment: any system >Reporter: Marc Wilhelm >Priority: Blocker > > Webdav connections through a http-proxy are currently not possible. > The webdav provider opens first a connection to the target system and checks > after this, if a proxy should be used. > To fix this in the method > "org.apache.maven.wagon.providers.webdav.WebdavWagon#openConnection()" the > call "webdavResource = new CorrectedWebdavResource( httpURL );" must be > changed into "webdavResource = new CorrectedWebdavResource( );" and after > configuring the http-proxy the method call > "webdavResource.setHttpURL(httpURL);" must be added. -- 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: (MEAR-35) Generate id for modules in application.xml
[ http://jira.codehaus.org/browse/MEAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94324 ] Olexandr Zakordonskyy commented on MEAR-35: --- Its requirement for websphere specific deployment descriptors like ibm-ejb-jar-ext.xmi. > Generate id for modules in application.xml > -- > > Key: MEAR-35 > URL: http://jira.codehaus.org/browse/MEAR-35 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Manikandan Balasubramanian >Priority: Minor > Fix For: 2.4 > > Attachments: MEAR-35-maven-ear-plugin.patch > > > When the ear plugin generates application.xml, it should generate an "id" > with each module. This "id" is according to application.xml schema. > This would help eclipse plugin to generate correct eclipse metedata. -- 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-82) wagon-webdav does not set http-proxy correctly
[ http://jira.codehaus.org/browse/WAGON-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94322 ] Marc Wilhelm commented on WAGON-82: --- yepp. I am actually setting up a new testcase which uses a proxy connection to verify the patch. when its done, i will upload the patch. > wagon-webdav does not set http-proxy correctly > -- > > Key: WAGON-82 > URL: http://jira.codehaus.org/browse/WAGON-82 > Project: wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 1.0-beta-2 > Environment: any system >Reporter: Marc Wilhelm >Priority: Blocker > > Webdav connections through a http-proxy are currently not possible. > The webdav provider opens first a connection to the target system and checks > after this, if a proxy should be used. > To fix this in the method > "org.apache.maven.wagon.providers.webdav.WebdavWagon#openConnection()" the > call "webdavResource = new CorrectedWebdavResource( httpURL );" must be > changed into "webdavResource = new CorrectedWebdavResource( );" and after > configuring the http-proxy the method call > "webdavResource.setHttpURL(httpURL);" must be added. -- 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: (MGPG-7) Ability to sign jars when using deploy:deploy-file
[ http://jira.codehaus.org/browse/MGPG-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94327 ] Daniel Kulp commented on MGPG-7: I've been thinking about this a bit more... Would this be acceptable:I can probably add a "gpg:sign-and-deploy-file" mojo that would just subclass the deploy-file mojo and sign everything it deploys.It would take all the same flags as deploy-file (and the added gpg ones) so should be a "drop in" replacement for deploy:deploy-file. > Ability to sign jars when using deploy:deploy-file > -- > > Key: MGPG-7 > URL: http://jira.codehaus.org/browse/MGPG-7 > Project: Maven 2.x GPG Plugin > Issue Type: Improvement >Affects Versions: 1.0-alpha-3 >Reporter: Wendy Smoak > > We need to be able to deploy signatures alongside jars that were not built > with Maven. > For example, Apache Tomcat is built with Ant, but they would like to deploy > signed jars to the ASF repo to be synced to central. Because of the > signature requirement, they are currently hosting a separate repository under > their website. > Something like "mvn deploy:deploy-file gpg:sign -D..." should work. -- 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-1504) Sonar plugin - release 0.2
Sonar plugin - release 0.2 -- Key: MAVENUPLOAD-1504 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1504 Project: maven-upload-requests Issue Type: Task Reporter: Simon Brandhof http://sonar.hortis.ch/download/sonar-0.2-bundle.jar http://sonar.hortis.ch/download/sonar-commons-0.2-bundle.jar http://sonar.hortis.ch/download/sonar-maven-plugin-0.2-bundle.jar http://sonar.hortis.ch http://sonar.hortis.ch/community/team/ Sonar is a continuous quality control tool for Java applications. The maven2 plugin collects metrics that are analyzed and historized in a centralized database. It is bundled with a GPL license. -- 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: (MEAR-63) Allow subclasses of EarMojo to provide a JarArchiver
Allow subclasses of EarMojo to provide a JarArchiver Key: MEAR-63 URL: http://jira.codehaus.org/browse/MEAR-63 Project: Maven 2.x Ear Plugin Issue Type: Improvement Affects Versions: 2.3 Environment: Maven 2.x Ear Plugin trunk : http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-ear-plugin r533087 Reporter: Elliot Metsger Priority: Minor Attachments: EarMojo.diff We would like to have the EAR plugin use a custom JarArchiver. In Maven 2.0.x, Plexus component lookups for our custom JarArchiver component fail randomly (I'm told by one of the Maven developers in the Maven chatroom on irc.codehaus.org that this behavior is fixed in Maven 2.1). Could the EAR plugin provide a protected method (for extending classes to override) which obtains the JarArchiver? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1257) Identification page lock
Identification page lock Key: CONTINUUM-1257 URL: http://jira.codehaus.org/browse/CONTINUUM-1257 Project: Continuum Issue Type: Bug Components: Web - Security, Web - UI Affects Versions: 1.1-alpha-1 Environment: Web interface on Firefox or Mozilla (can't test on IE) Reporter: Charles Paulet Priority: Minor 1 - The root user create a new user (projectleader) with a password ans sets privileges. 2 - The root user logs out. 3 - The projectleader logs in, AND checks the "remember me" checkbox. 4 - Continuum asks to change the projectleader password Here if you don't delete the cookie, you can't exit the security/password.action page. - Logout doesn't work - Restart Continuum doesn't work - Click menu item doesn't work It seems, the 'remember me' checkbox set the login valid. But, we can't avoid, override or bypass the security check afterward. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-1258) Configure the possibility of resolving or not the search of build executables (maven, ant ...)
Configure the possibility of resolving or not the search of build executables (maven, ant ...) -- Key: CONTINUUM-1258 URL: http://jira.codehaus.org/browse/CONTINUUM-1258 Project: Continuum Issue Type: Wish Components: Environmental, Integration - Ant Affects Versions: 1.1-alpha-1 Environment: anyone i tested only on Redhat Reporter: Charles Paulet Priority: Critical When continuum 1.1 starts, logs contains : 2007-04-26 11:55:45,827 [main] WARN ContinuumBuildExecutor:maven-1 - Could not find the executable 'maven' in the path '[$PATH]'. 2007-04-26 11:55:45,833 [main] INFO ContinuumBuildExecutor:ant - Resolved the executable 'ant' to '/usr/bin/ant'. 2007-04-26 11:55:46,600 [main] WARN ContinuumBuildExecutor:maven2 - Could not find the executable 'mvn' in the path '[$PATH]'. This search override any alias defined in a user environment. This search follows the PATH definition order We want to use another ant with Continuum (using a shell script to launch ant in a specific environnement) We can't change the Path order because of internal conflicts. It would be fine if the Continuum configuration contains a "check path for build executables" parameter. -- 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-2864) Optional is not transitive
[ http://jira.codehaus.org/browse/MNG-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94345 ] Carlos Sanchez commented on MNG-2864: - what version of maven are you using? > Optional is not transitive > -- > > Key: MNG-2864 > URL: http://jira.codehaus.org/browse/MNG-2864 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Reporter: Bernhard Mähr >Priority: Minor > > Hello! > I have this situation: > WAR > |- compile/optional> POM compile ---> JAR1 > |- compile/optional> JAR2 > If I build WAR I get a war-file with the Manifest entries JAR1 and JAR2 and > the file JAR1 in WEB-INF\lib. > I would expect a war-file with the Manifest entries JAR1 and JAR2 and no > WEB-INF\lib. > It seams to me that JAR1 is included because the second dependency is > without optional and the optional from the frist dependency is not transitive > to the second dependency. > Generally I think it is a hack to use the combination compile/optional to > decide a lib should be included in Manifest but not in the lib dir. I think > the should be an additional scope betwen compile and provided for this > purpose. > Bernhard Mähr -- 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-2192) Transitive dependency overrides version specified in POM
[ http://jira.codehaus.org/browse/MNG-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MNG-2192. --- Assignee: Carlos Sanchez Resolution: Cannot Reproduce Fix Version/s: (was: 2.1.x) without more info this can't be reproduced > Transitive dependency overrides version specified in POM > > > Key: MNG-2192 > URL: http://jira.codehaus.org/browse/MNG-2192 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0.2, 2.0.3 >Reporter: Ray Ward >Assignee: Carlos Sanchez > > I'm seeing this in both 2.0.2 and 2.0.3, but not in 1.0.2. I specify a > version for a dependency in the parent pom.xml. As the build goes on, one or > more dependencies will be processed in the modules that have earlier > versions, and those earlier versions override the version I specified in > pom.xml. > > For example: > > commons-collections > commons-collections > 3.1 > > > Then from the log: > ... > [DEBUG] struts:struts:jar:1.2.4:compile (selected for compile) > [DEBUG] oro:oro:jar:2.0.7:compile (selected for compile) > [DEBUG] commons-logging:commons-logging:jar:1.0.4:compile (selected for > compile) > [DEBUG] commons-fileupload:commons-fileupload:jar:1.0:compile (selected > for compile) > [DEBUG] commons-collections:commons-collections:jar:2.1:compile (selected > for compile) > [DEBUG] commons-beanutils:commons-beanutils:jar: 1.6.1:compile (selected > for compile) > [DEBUG] commons-logging:commons-logging:jar:1.0:compile (removed - > nearer found: 1.0.4) > [DEBUG] commons-collections:commons-collections:jar:2.0:compile > (removed - nearer found: 2.1) > [DEBUG] commons-digester:commons-digester:jar:1.5:compile (selected for > compile) > [DEBUG] commons-beanutils:commons-beanutils:jar:1.6:compile (removed - > nearer found: 1.6.1) > ... > > And what is in the WAR file is: > [DEBUG] adding entry WEB-INF/lib/commons-collections-2.1.jar > (verified this from the .war file) > > This is contrary to the documentation on the web site: > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > Which says: > Dependency mediation - this determines what version of a dependency will be > used when multiple versions of an artifact are encountered. Currently, Maven > 2.0 only supports using the "nearest definition" - so you can always > guarantee a version by declaring it explicitly in your project's POM. > I take this to mean that the POM is based on the parent pom.xml in a > multiproject build, and the modules should inherit the version setting from > the parent. So I haven't tried to specify the version again in a child > pom.xml. > I came across this while converting a project from M1 to M2. The M1 WAR file > contains version 3.1, as expected. > Hope to include a simple pom.xml to demo this later -- schedule crunch at the > moment precludes doing it now. -- 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-2007) Exported POM still has dependency version ranges
[ http://jira.codehaus.org/browse/MNG-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94349 ] Carlos Sanchez commented on MNG-2007: - it'd be good if help:effective-pom (or maybe a new goal) reflects also the pom after resolution, with locked down versions > Exported POM still has dependency version ranges > > > Key: MNG-2007 > URL: http://jira.codehaus.org/browse/MNG-2007 > Project: Maven 2 > Issue Type: Bug > Components: maven-archiver >Affects Versions: 2.0.2 >Reporter: Matthew Beermann > Fix For: 2.0.x > > > If you have a version range for one of your dependencies, then the exported > POM (the one that's placed in the repository and in the jar itself) will > still have a range there. This seems at odds with (one) point of exporting a > POM, which is to have all the information you need to reconstruct the state > of a build at a particular moment in time. Without knowing which version > number was chosen, you can't be sure you're reconstructing the same build > later. > It also seems to be at odds with the behavior elsewhere in this exported > artifact: the plugins section shows the actual version number used, and > active profiles are quietly merged into the main 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] Updated: (MNG-2966) Use optional transitive dependencies versions as dependencyManagement does
[
http://jira.codehaus.org/browse/MNG-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez updated MNG-2966:
Description:
I would like to be able to add an includes statement on a dependency to get its
optional dependency(ies).
ie:
hibernate
hibernate
3.2.1.ga
jgroups
jgroups-all
runtime
false
For example, I use hibernate 3.2.1.ga, it has an optional dependency on
jgroups-all-2.2.8.
I would like to be able to add an inclusion statement on the hibernate lib to
tell that I want to include jgroups as well.
The main reason for this is that I want the same version as specified in the
hibernate pom.
This way, upgrading hibernate would also upgrade my version of jgroups at the
same time.
Obviously, we need to be able to define a scope and optional attribute as well
(not inherited)
Or maybe we could set the dependency explicitly in the pom without specifying
the version and have maven resolve the version from the nearest source (as it
does normally) automatically or we specify where to resolve it.
ie something like:
jgroups
jgroups-all
hibernate
hibernate
${hibernate.version}
runtime
false
was:
I would like to be able to add an includes statement on a dependency to get its
optional dependency(ies).
ie:
hibernate
hibernate
3.2.1.ga
jgroups
jgroups-all
runtime
false
For example, I use hibernate 3.2.1.ga, it has an optional dependency on
jgroups-all-2.2.8.
I would like to be able to add an inclusion statement on the hibernate lib to
tell that I want to include jgroups as well.
The main reason for this is that I want the same version as specified in the
hibernate pom.
This way, upgrading hibernate would also upgrade my version of jgroups at the
same time.
Obviously, we need to be able to define a scope and optional attribute as well
(not inherited)
Or maybe we could set the dependency explicitly in the pom without specifying
the version and have maven resolve the version from the nearest source (as it
does normally) automatically or we specify where to resolve it.
ie something like:
jgroups
jgroups-all
hibernate
hibernate
${hibernate.version}
runtime
false
Affects Version/s: 2.0.6
Summary: Use optional transitive dependencies versions as
dependencyManagement does (was: Get optional transitive dependencies)
Basically you're asking to use optional dependencies versions as if they were
defined in the dependencyManagement section
> Use optional transitive dependencies versions as dependencyManagement does
> --
>
> Key: MNG-2966
> URL: http://jira.codehaus.org/browse/MNG-2966
> Project: Maven 2
> Issue Type: Improvement
> Components: Dependencies
>Affects Versions: 2.0.6
>Reporter: Daniel Beland
>
> I would like to be able to add an includes statement on a dependency to get
> its optional dependency(ies).
> ie:
>
> hibernate
> hibernate
> 3.2.1.ga
>
>
> jgroups
> jgroups-all
> runtime
> false
>
>
>
> For example, I use hibernate 3.2.1.ga, it has an optional dependency on
> jgroups-all-2.2.8.
> I would like to be able to add an inclusion statement on the hibernate lib to
> tell that I want to include jgroups as well.
> The main reason for this is that I want the same version as specified in the
> hibernate pom.
> This way, upgrading hibernate would also upgrade my version of jgroups at the
> same time.
> Obviously, we need to be able to define a scope and optional attribute as
> well (not inherited)
> Or maybe we could set the dependency explicitly in the pom without specifying
> the version and have maven resolve the version from the nearest source (as it
> does normally) automatically or we specify where to resolve it.
> ie something like:
>
> jgroups
> jgroups-all
>automatically or we need to tell maven where to find it -->
>
> hibernate
> hibernate
>
> ${hibernate.version}
>
> runtime
> false
>
--
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-2965) Update svn:ignores for developing with eclipse
[
http://jira.codehaus.org/browse/MNG-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MNG-2965.
---
Assignee: Carlos Sanchez
Resolution: Fixed
Fix Version/s: 2.1-alpha-1
2.0.7
> Update svn:ignores for developing with eclipse
> --
>
> Key: MNG-2965
> URL: http://jira.codehaus.org/browse/MNG-2965
> Project: Maven 2
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 2.0.7
>Reporter: Mark Hobson
>Assignee: Carlos Sanchez
> Fix For: 2.0.7, 2.1-alpha-1
>
>
> Need to add the following to their respective svn:ignore properties:
> {noformat}
> ? maven-artifact-manager\.settings
> ? maven-artifact-test\.settings
> ? maven-artifact\.settings
> ? maven-core\.settings
> ? maven-error-diagnostics\.settings
> ? maven-model\.settings
> ? maven-monitor\.settings
> ? maven-plugin-api\.settings
> ? maven-plugin-descriptor\.settings
> ? maven-plugin-parameter-documenter\.settings
> ? maven-plugin-registry\.settings
> ? maven-profile\.settings
> ? maven-project\.settings
> ? maven-reporting\maven-reporting-api\.settings
> ? maven-repository-metadata\.settings
> ? maven-script\maven-script-ant\.classpath
> ? maven-script\maven-script-ant\.project
> ? maven-script\maven-script-ant\.settings
> ? maven-script\maven-script-beanshell\.settings
> ? maven-settings\.settings
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MNG-2965) Update svn:ignores for developing with eclipse
[
http://jira.codehaus.org/browse/MNG-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hobson reopened MNG-2965:
--
Missed a few:
{noformat}
? maven-artifact-manager\.settings
? maven-artifact-test\.settings
? maven-plugin-registry\.settings
? maven-repository-metadata\.settings
? maven-script\maven-script-ant\.classpath
? maven-script\maven-script-ant\.project
? maven-script\maven-script-ant\.settings
{noformat}
> Update svn:ignores for developing with eclipse
> --
>
> Key: MNG-2965
> URL: http://jira.codehaus.org/browse/MNG-2965
> Project: Maven 2
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 2.0.7
>Reporter: Mark Hobson
>Assignee: Carlos Sanchez
> Fix For: 2.0.7, 2.1-alpha-1
>
>
> Need to add the following to their respective svn:ignore properties:
> {noformat}
> ? maven-artifact-manager\.settings
> ? maven-artifact-test\.settings
> ? maven-artifact\.settings
> ? maven-core\.settings
> ? maven-error-diagnostics\.settings
> ? maven-model\.settings
> ? maven-monitor\.settings
> ? maven-plugin-api\.settings
> ? maven-plugin-descriptor\.settings
> ? maven-plugin-parameter-documenter\.settings
> ? maven-plugin-registry\.settings
> ? maven-profile\.settings
> ? maven-project\.settings
> ? maven-reporting\maven-reporting-api\.settings
> ? maven-repository-metadata\.settings
> ? maven-script\maven-script-ant\.classpath
> ? maven-script\maven-script-ant\.project
> ? maven-script\maven-script-ant\.settings
> ? maven-script\maven-script-beanshell\.settings
> ? maven-settings\.settings
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MWAR-64) resource processing does not occur correct hierarchical modules.
[ http://jira.codehaus.org/browse/MWAR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94355 ] Heinrich Nirschl commented on MWAR-64: -- I think, this is just a workaround and not the solution. A relative name should always have the same meaning independently from where you start your build. > resource processing does not occur correct hierarchical modules. > > > Key: MWAR-64 > URL: http://jira.codehaus.org/browse/MWAR-64 > Project: Maven 2.x War Plugin > Issue Type: Bug >Affects Versions: 2.0.1 > Environment: Windows XP >Reporter: Brian Keyser > > I have a project that is similar to > + - ProjectA >| >- pom.xml >| >+ ProjectB > | > - pom.xml > Within the pom.xml for ProjectB there is an entry describing additional > resources to include in the war > ... > > org.apache.maven.plugins > maven-war-plugin > > > > src/main/resources > true > > > > > ... > When running 'mvn install' from the project A directory, I get the following > error > ... > [INFO] Copy webapp webResources to > C:\thinktank\thinktank-d1.1.0\server\server-webapp\target\server-webapp-1.1.0-SNAPSHOT > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] basedir src\main\resources does not exist > [INFO] > > [DEBUG] Trace > java.lang.IllegalStateException: basedir src\main\resources does not exist > at > org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:542) > at > org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles(AbstractWarMojo.java:810) > at > org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:437) > at > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:355) > at > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:161) > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:127) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > 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) > However, if I change the to > ... > projectb/src/main/resources > ... > The install goal works fine. > If I run 'mvn install' from projectb with the first configuration it does > perform an install, ie, when the directory is configured as > 'src/main/resources'. Seems like there is a problem in reading the base > directory for hierarchical projects. > Thanks for taking a look at this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2965) Update svn:ignores for developing with eclipse
[
http://jira.codehaus.org/browse/MNG-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MNG-2965.
---
Resolution: Fixed
> Update svn:ignores for developing with eclipse
> --
>
> Key: MNG-2965
> URL: http://jira.codehaus.org/browse/MNG-2965
> Project: Maven 2
> Issue Type: Improvement
> Components: Bootstrap & Build
>Affects Versions: 2.0.7
>Reporter: Mark Hobson
>Assignee: Carlos Sanchez
> Fix For: 2.0.7, 2.1-alpha-1
>
>
> Need to add the following to their respective svn:ignore properties:
> {noformat}
> ? maven-artifact-manager\.settings
> ? maven-artifact-test\.settings
> ? maven-artifact\.settings
> ? maven-core\.settings
> ? maven-error-diagnostics\.settings
> ? maven-model\.settings
> ? maven-monitor\.settings
> ? maven-plugin-api\.settings
> ? maven-plugin-descriptor\.settings
> ? maven-plugin-parameter-documenter\.settings
> ? maven-plugin-registry\.settings
> ? maven-profile\.settings
> ? maven-project\.settings
> ? maven-reporting\maven-reporting-api\.settings
> ? maven-repository-metadata\.settings
> ? maven-script\maven-script-ant\.classpath
> ? maven-script\maven-script-ant\.project
> ? maven-script\maven-script-ant\.settings
> ? maven-script\maven-script-beanshell\.settings
> ? maven-settings\.settings
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MJAR-71) use manifest in classesdir/META-INF if exists
use manifest in classesdir/META-INF if exists
-
Key: MJAR-71
URL: http://jira.codehaus.org/browse/MJAR-71
Project: Maven 2.x Jar Plugin
Issue Type: Improvement
Affects Versions: 2.1
Reporter: Carlos Sanchez
Fix For: 2.2
With 2.1 I need to add this to the pom to use the manifest that it's already in
the classes folder, make this the default
org.apache.maven.plugins
maven-jar-plugin
2.1
${project.build.outputDirectory}/META-INF/MANIFEST.MF
--
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-54) add targetPath support on the webResources plugin parameter
[ http://jira.codehaus.org/browse/MWAR-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94357 ] Jay Goldman commented on MWAR-54: - It does not appear to be working in 2.0.2. Based upon comments in _War overlay can overwrite files in dependant war artifact_ I replaced the use of copyFileIfModified in copyResources with an unconditional copy (with an explicit creation of any needed directories first) and the files are copied to the correct location. So I think there is something wrong in copyFileIfModified when the target file does not exist (haven't checked the behavior when the target file already exists). > add targetPath support on the webResources plugin parameter > --- > > Key: MWAR-54 > URL: http://jira.codehaus.org/browse/MWAR-54 > Project: Maven 2.x War Plugin > Issue Type: New Feature >Reporter: Marvin King >Assignee: Marvin King > Fix For: 2.0.2 > > Attachments: MWAR-54-maven-war-plugin.patch > > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > -- 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-136) The plugin does not use JAVA_HOME variable and launches default JVM
[ http://jira.codehaus.org/browse/SUREFIRE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Somov closed SUREFIRE-136. - Resolution: Fixed > The plugin does not use JAVA_HOME variable and launches default JVM > --- > > Key: SUREFIRE-136 > URL: http://jira.codehaus.org/browse/SUREFIRE-136 > Project: Maven Surefire > Issue Type: Improvement > Environment: Windows 2000, Maven 2.0.4 >Reporter: Andrey Somov >Priority: Minor > Fix For: 2.4 > > Attachments: MSUREFIREREP-25.log > > > The plugin does not use JAVA_HOME variable and launches default JVM (in this > case default is not defined): > [INFO] Surefire report directory: > D:\tools\workspace\DB2Monster\monster-axis\target\surefire-reports > 'java' is not recognized as an internal or external command, > operable program or batch file. > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > JAVA_HOME does not necessary point to the default JVM. > The plugin shall use the same JVM as 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: (MNG-2967) Uber embedder contains wrong manifest
Uber embedder contains wrong manifest - Key: MNG-2967 URL: http://jira.codehaus.org/browse/MNG-2967 Project: Maven 2 Issue Type: Bug Components: Embedding Affects Versions: 2.1-alpha-1 Reporter: Carlos Sanchez Seems that shade puts a manifest from a random jar instead of the one from the project 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: (MNG-2967) Uber embedder contains wrong manifest
[ http://jira.codehaus.org/browse/MNG-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MNG-2967: Fix Version/s: 2.1-alpha-1 > Uber embedder contains wrong manifest > - > > Key: MNG-2967 > URL: http://jira.codehaus.org/browse/MNG-2967 > Project: Maven 2 > Issue Type: Bug > Components: Embedding >Affects Versions: 2.1-alpha-1 >Reporter: Carlos Sanchez > Fix For: 2.1-alpha-1 > > > Seems that shade puts a manifest from a random jar instead of the one from > the project 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: (CONTINUUM-1255) FATAL EnvironmentCheck Failure on Continuum Startup
[ http://jira.codehaus.org/browse/CONTINUUM-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94372 ] Gabriel Misura commented on CONTINUUM-1255: --- Yeah, its working. That's why I marked it pretty low. Er, i thought I did. > FATAL EnvironmentCheck Failure on Continuum Startup > --- > > Key: CONTINUUM-1255 > URL: http://jira.codehaus.org/browse/CONTINUUM-1255 > Project: Continuum > Issue Type: Sub-task >Affects Versions: 1.1-alpha-1 > Environment: JBoss 4.0.5.GA, JDK 1.4.2_12 >Reporter: Gabriel Misura > > 42734 [http-0.0.0.0-8080-1] INFO > org.codehaus.plexus.security.system.check.EnvironmentCheck:required-roles - > Checking the existance of required roles. > 43501 [http-0.0.0.0-8080-1] FATAL > com.opensymphony.xwork.interceptor.Interceptor:pssEnvironmentCheckInterceptor > - EnvironmentCheck Failure. > == > ENVIRONMENT FAILURE !! > Missing "/security" package namespace in xwork.xml > Missing [1] xwork.xml configuration elements. > == > 43651 [http-0.0.0.0-8080-1] INFO > com.opensymphony.xwork.interceptor.Interceptor:pssSecureActionInterceptor - > org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor > initialized! > 43876 [http-0.0.0.0-8080-1] INFO > com.opensymphony.xwork.interceptor.Interceptor:pssSecureActionInterceptor - > org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor > initialized! > 43886 [http-0.0.0.0-8080-1] INFO > com.opensymphony.xwork.interceptor.Interceptor:pssSecureActionInterceptor - > org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor > initialized! > 45228 [http-0.0.0.0-8080-1] INFO > com.opensymphony.xwork.interceptor.Interceptor:pssForceAdminUserInterceptor > - Admin user found. No need to configure admin user. > 49640 [http-0.0.0.0-8080-2] INFO > com.opensymphony.webwork.views.freemarker.FreemarkerManager - Instantiating > Freemarker ConfigManager!, > com.opensymphony.webwork.views.freemarker.FreemarkerManager -- 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: (MECLIPSE-262) Maven compilation and eclipse classpath don't match
Maven compilation and eclipse classpath don't match --- Key: MECLIPSE-262 URL: http://jira.codehaus.org/browse/MECLIPSE-262 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: dependency resolution Affects Versions: 2.3 Environment: Maven 2.0.6, 2.0.4 Reporter: Carlos Sanchez Attachments: compile.txt, eclipse.txt https://svn.apache.org/repos/asf/maven/components/trunk/maven-core rev# 533182 compile uses plexus-component-api-1.0-alpha-24 (the right one) eclipse:eclipse uses plexus-component-api-1.0-alpha-16 -- 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: (MECLIPSE-262) Maven compilation and eclipse classpath don't match
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MECLIPSE-262: Attachment: eclipse.txt compile.txt debug output > Maven compilation and eclipse classpath don't match > --- > > Key: MECLIPSE-262 > URL: http://jira.codehaus.org/browse/MECLIPSE-262 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution >Affects Versions: 2.3 > Environment: Maven 2.0.6, 2.0.4 >Reporter: Carlos Sanchez > Attachments: compile.txt, eclipse.txt > > > https://svn.apache.org/repos/asf/maven/components/trunk/maven-core rev# 533182 > compile uses plexus-component-api-1.0-alpha-24 (the right one) > eclipse:eclipse uses plexus-component-api-1.0-alpha-16 -- 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: (MECLIPSE-262) Maven compilation and eclipse classpath don't match with conflicting versions at same dependency depth
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MECLIPSE-262: Summary: Maven compilation and eclipse classpath don't match with conflicting versions at same dependency depth (was: Maven compilation and eclipse classpath don't match) > Maven compilation and eclipse classpath don't match with conflicting versions > at same dependency depth > -- > > Key: MECLIPSE-262 > URL: http://jira.codehaus.org/browse/MECLIPSE-262 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution >Affects Versions: 2.3 > Environment: Maven 2.0.6, 2.0.4 >Reporter: Carlos Sanchez > Attachments: compile.txt, eclipse.txt > > > https://svn.apache.org/repos/asf/maven/components/trunk/maven-core rev# 533182 > compile uses plexus-component-api-1.0-alpha-24 (the right one) > eclipse:eclipse uses plexus-component-api-1.0-alpha-16 -- 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-262) Maven compilation and eclipse classpath don't match
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94376 ] Carlos Sanchez commented on MECLIPSE-262: - i think the problem is that maven-core depends on - plexus-container-default:1.0-alpha-24 - plexus-active-collections:1.0-beta-1 that in turn depend on plexus-container-api 1.0-alpha-24 and 1.0-alpha-19 respectively so both are at same level, the problem so which one wins is undefined, but at lease eclipse and compiler plugin should behave the same > Maven compilation and eclipse classpath don't match > --- > > Key: MECLIPSE-262 > URL: http://jira.codehaus.org/browse/MECLIPSE-262 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution >Affects Versions: 2.3 > Environment: Maven 2.0.6, 2.0.4 >Reporter: Carlos Sanchez > Attachments: compile.txt, eclipse.txt > > > https://svn.apache.org/repos/asf/maven/components/trunk/maven-core rev# 533182 > compile uses plexus-component-api-1.0-alpha-24 (the right one) > eclipse:eclipse uses plexus-component-api-1.0-alpha-16 -- 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-262) Maven compilation and eclipse classpath don't match with conflicting versions at same dependency depth
[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94377 ] Carlos Sanchez commented on MECLIPSE-262: - I added plexus-component-api:1.0-alpha-24 to the parent pom dependency management section as a workaround > Maven compilation and eclipse classpath don't match with conflicting versions > at same dependency depth > -- > > Key: MECLIPSE-262 > URL: http://jira.codehaus.org/browse/MECLIPSE-262 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution >Affects Versions: 2.3 > Environment: Maven 2.0.6, 2.0.4 >Reporter: Carlos Sanchez > Attachments: compile.txt, eclipse.txt > > > https://svn.apache.org/repos/asf/maven/components/trunk/maven-core rev# 533182 > compile uses plexus-component-api-1.0-alpha-24 (the right one) > eclipse:eclipse uses plexus-component-api-1.0-alpha-16 -- 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: (SCM-305) release:perform fails on linux
[ http://jira.codehaus.org/browse/SCM-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Schneider closed SCM-305. - Resolution: Fixed Fix Version/s: 1.0 > release:perform fails on linux > -- > > Key: SCM-305 > URL: http://jira.codehaus.org/browse/SCM-305 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce >Affects Versions: 1.0-beta-3 > Environment: Maven 2.0.6 > Linux (Fedora Core release 4) > IBM JDK 1.4.2 SR7 >Reporter: Patrick Schneider >Assignee: Patrick Schneider >Priority: Critical > Fix For: 1.0 > > Attachments: maven-scm-provider-perforce-release-perform-error.txt > > > When attempting a 'release:perform' from Linux, if using Perforce, the > command fails. -X output attached. > The provider is attempting to create/save a clientspec using forward slashes, > which Perforce does not allow. See generateDefaultClientspecName in > PerforceScmProvider.java. -- 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-1501) Upload UrlRewriteFilter 3.0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94379 ] Paul Tuckey commented on MAVENUPLOAD-1501: -- GroupId (now tuckey.org) and ArtifactId fixed (now urlrewritefilter). Jar re-uploaded to http://tuckey.org/urlrewrite/dist/urlrewritefilter-3.0.4-maven-bundle.jar Note, org.tuckey - urlrewritefilter (valid) org.tuckey - urlrewrite (invalid) net.java.dev.urlrewrite - urlrewritefilter (invalid) > Upload UrlRewriteFilter 3.0.4 > - > > Key: MAVENUPLOAD-1501 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1501 > Project: maven-upload-requests > Issue Type: Task >Reporter: Paul Tuckey > > UrlRewriteFilter > Based on the popular and very useful mod_rewrite for apache, UrlRewriteFilter > is a Java Web Filter for any J2EE > compliant web application server (such as Resin, Orion or Tomcat), which > allows you to rewrite URLs before they get to > your code. It is a very powerful tool just like Apache's mod_rewrite. -- 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-2968) Forbid dots in artifactId
Forbid dots in artifactId - Key: MNG-2968 URL: http://jira.codehaus.org/browse/MNG-2968 Project: Maven 2 Issue Type: Improvement Components: POM Affects Versions: 2.0.6, 2.1-alpha-1 Reporter: Carlos Sanchez Fix For: 2.1-alpha-1 artifactIds with dots are potential trouble. They prevent using groupId.artifactId as identifier and later parse it back -- 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-2968) Forbid dots in artifactId
[ http://jira.codehaus.org/browse/MNG-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MNG-2968: Fix Version/s: 2.1-alpha-1 For instance org.mortbay.jetty:servlet-api-2.5 > Forbid dots in artifactId > - > > Key: MNG-2968 > URL: http://jira.codehaus.org/browse/MNG-2968 > Project: Maven 2 > Issue Type: Improvement > Components: POM >Affects Versions: 2.0.6, 2.1-alpha-1 >Reporter: Carlos Sanchez > Fix For: 2.1-alpha-1 > > > artifactIds with dots are potential trouble. They prevent using > groupId.artifactId as identifier and later parse it back -- 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-1112) Unable to use DB without username and password
[ http://jira.codehaus.org/browse/CONTINUUM-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94395 ] Napoleon Esmundo C. Ramirez commented on CONTINUUM-1112: This isn't a Continuum issue. To enable "null" users, or more known as anonymous users, privileges on the database must be granted to it. To make your configuration work, you'll have to do something like: mysql> GRANT ALL PRIVILEGES ON test TO ''@'localhost'; mysql> FLUSH PRIVILEGES; > Unable to use DB without username and password > -- > > Key: CONTINUUM-1112 > URL: http://jira.codehaus.org/browse/CONTINUUM-1112 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.1-alpha-1 > Environment: mysql jdbc driver 5.0.3, mysql server 5.0.24 >Reporter: Carlos Sanchez > Fix For: 1.1-alpha-# > > Attachments: log.txt > > > Changed plexus.conf database definition to use mysql db that anyone can > access (no user / no password) and got an error because it's trying to use a > null username. > java.sql.SQLException: Access denied for user 'null'@'localhost' (using > password: YES) > > jdbc/continuum > javax.sql.DataSource > > > driverClassName > com.mysql.jdbc.Driver > > > url > jdbc:mysql://localhost/test > > > username > > > > password > > > > -- 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-1112) Unable to use DB without username and password
[ http://jira.codehaus.org/browse/CONTINUUM-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94399 ] Carlos Sanchez commented on CONTINUUM-1112: --- the problem was that it was trying to use the string "null" as username > Unable to use DB without username and password > -- > > Key: CONTINUUM-1112 > URL: http://jira.codehaus.org/browse/CONTINUUM-1112 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.1-alpha-1 > Environment: mysql jdbc driver 5.0.3, mysql server 5.0.24 >Reporter: Carlos Sanchez > Fix For: 1.1-alpha-# > > Attachments: log.txt > > > Changed plexus.conf database definition to use mysql db that anyone can > access (no user / no password) and got an error because it's trying to use a > null username. > java.sql.SQLException: Access denied for user 'null'@'localhost' (using > password: YES) > > jdbc/continuum > javax.sql.DataSource > > > driverClassName > com.mysql.jdbc.Driver > > > url > jdbc:mysql://localhost/test > > > username > > > > password > > > > -- 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
