[jira] Commented: (MWAR-104) handle zip dependencies in war plugin
[ http://jira.codehaus.org/browse/MWAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106048 ] Tuomas Kiviaho commented on MWAR-104: - Codebase has changed quite dramatically and this patch doesn't apply well anymore. handle zip dependencies in war plugin - Key: MWAR-104 URL: http://jira.codehaus.org/browse/MWAR-104 Project: Maven 2.x War Plugin Issue Type: Improvement Environment: all Reporter: Olivier Lamy Attachments: foobar.zip, MWAR-104 As MNG-1683 has been applied, the zip artifact must be handled in the war plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-432) Proxy Connectors are unable to download artifacts with alpha numerical version numbers
[ http://jira.codehaus.org/browse/MRM-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106055 ] Marc Wilhelm commented on MRM-432: -- Same to me. I am working only with default layout. Proxy Connectors are unable to download artifacts with alpha numerical version numbers -- Key: MRM-432 URL: http://jira.codehaus.org/browse/MRM-432 Project: Archiva Issue Type: Bug Components: remote proxy Affects Versions: 1.0-alpha-2 Environment: Solaris 5.9, java 1.5.0_11, maven 2.0.7 Reporter: Mathias Arens Assignee: Joakim Erdfelt Priority: Critical Fix For: 1.0-beta-2 Archiva is unable to download this artifact: dependency groupIdch.ethz.ganymed/groupId artifactIdganymed-ssh2/artifactId versionbuild210/version /dependency although it is in the central repository. I can download the artifact if a switch the central mirror of, just downloading the artifact directly over maven. I didn't had any problems with all the other artifacts from the central repository. I assume that there is a problem with alpha numerical version numbers. But it's just a guess. -- 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-104) handle zip dependencies in war plugin
[ http://jira.codehaus.org/browse/MWAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106057 ] Tuomas Kiviaho commented on MWAR-104: - I considered doing exactly the same to the patch myself, but the change was just too radical for me to fully comprehend at the moment (although I liked the improved quality). I'd be happy if you could provide at least patch for now to re-enable Olivier's zip support. 2.1-alpha-1 feels like being too far away. Enablement/disablement of zip overlays could be the answer, but that smells big time at least if done simply by a property. handle zip dependencies in war plugin - Key: MWAR-104 URL: http://jira.codehaus.org/browse/MWAR-104 Project: Maven 2.x War Plugin Issue Type: Improvement Environment: all Reporter: Olivier Lamy Assignee: Stephane Nicoll Fix For: 2.1-alpha-1 Attachments: foobar.zip, MWAR-104 As MNG-1683 has been applied, the zip artifact must be handled in the war plugin. -- 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-104) handle zip dependencies in war plugin
[ http://jira.codehaus.org/browse/MWAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106058 ] Stephane Nicoll commented on MWAR-104: -- Will do. I don't get your last remark regarding zip overlays. What are you suggesting? handle zip dependencies in war plugin - Key: MWAR-104 URL: http://jira.codehaus.org/browse/MWAR-104 Project: Maven 2.x War Plugin Issue Type: Improvement Environment: all Reporter: Olivier Lamy Assignee: Stephane Nicoll Fix For: 2.1-alpha-1 Attachments: foobar.zip, MWAR-104 As MNG-1683 has been applied, the zip artifact must be handled in the war plugin. -- 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-3171) performRelease=true breaks install/deploy with multimodule projects
performRelease=true breaks install/deploy with multimodule projects
---
Key: MNG-3171
URL: http://jira.codehaus.org/browse/MNG-3171
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.7
Reporter: Julien HENRY
Attachments: unTest.zip
Hi,
To build my project, I use:
mvn clean install -DperformRelease=true
In a multimodule project, it doesn't work if all dependencies are not already
in the local repository.
Step to reproduce:
1) create a multimodule project with moduleA and moduleB. moduleA depends on
moduleB.
2) Hit mvn clean install: should work
3) Clean your local repository (remove moduleA and moduleB)
4) Hit mvn clean install -DperformRelease=true:
{quote}
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - com.capgemini:unTest:pom:1.0-SNAPSHOT
[INFO] Unnamed - com.capgemini:moduleB:jar:1.0-SNAPSHOT
[INFO] Unnamed - com.capgemini:moduleA:jar:1.0-SNAPSHOT
[INFO]
[INFO] Building Unnamed - com.capgemini:unTest:pom:1.0-SNAPSHOT
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\test\unTest\target
[INFO] Deleting directory D:\test\unTest\target\classes
[INFO] Deleting directory D:\test\unTest\target\test-classes
[INFO] Deleting directory D:\test\unTest\target\site
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] Preparing javadoc:jar
[INFO]
[INFO] Building Unnamed - com.capgemini:unTest:pom:1.0-SNAPSHOT
[INFO]
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building Unnamed - com.capgemini:moduleB:jar:1.0-SNAPSHOT
[INFO]
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building Unnamed - com.capgemini:moduleA:jar:1.0-SNAPSHOT
[INFO]
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] snapshot com.capgemini:moduleB:1.0-SNAPSHOT: checking for updates from
illiade-maven-repository-snapshots
Downloading:
http://illiade.sud.capgemini.fr/maven2-snapshots/com/capgemini/moduleB/1.0-SNAPSHOT/moduleB-1.0-SNAPSHOT.jar
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) com.capgemini:moduleB:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.capgemini -DartifactId=moduleB \
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) com.capgemini:moduleA:jar:1.0-SNAPSHOT
2) com.capgemini:moduleB:jar:1.0-SNAPSHOT
--
1 required artifact is missing.
for artifact:
com.capgemini:moduleA:jar:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
illiade-maven-repository-snapshots
(http://illiade.sud.capgemini.fr/maven2-snapshots)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Aug 31 12:08:24 CEST 2007
[INFO] Final Memory: 6M/254M
[INFO]
{quote}
--
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: (MRM-392) pressing 'return' in the blacklist/whitelist form field submits whole form and validates, not pressing associated button
[ http://jira.codehaus.org/browse/MRM-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-392. Resolution: Fixed Fixed in -r571430, with the following changes in archiva-webapp/src/main/webapp/WEB-INF/jsp/admin/editProxyConnector.jsp: - Added javascript function for submitting the form to a specific action depending on which textfield the onKeyPress event was invoked - Added onkeypress action to the property, blacklist pattern and whitelist pattern textfields pressing 'return' in the blacklist/whitelist form field submits whole form and validates, not pressing associated button Key: MRM-392 URL: http://jira.codehaus.org/browse/MRM-392 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-alpha-1 Reporter: Brett Porter Assignee: Maria Odea Ching Priority: Critical Fix For: 1.0-beta-2 - add a proxy connector - don't fill in any fields - type foo into blacklist field - press return EXPECTED: add foo to blacklist ACTUAL: submits form, gives validation errors -- 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-2046) External property file in command line
[ http://jira.codehaus.org/browse/MNG-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106072 ] Adrian Petru Dimulescu commented on MNG-2046: - I completely agree, I spent hours searching for a way to externalize build properties only to find that Maven2 knowingly restricts this. You can't use external properties files nor external XML entities. I ended up describing my properties in the profiles.xml file which is the proper way to do it. In my case, I have unit tests that need to have access dynamically to some of those properties. If they were a properties file, it would have been extremely simple to read them. Now I have to code parsing profiles.xml ... I really think that being able to externalize properties is a good idea. Having a .properties file per developer with his own database etc. settings is really simple way of describing configuration. While I understand that Maven people want to avoid having multiple configuration locations and want to describe everything in the pom, I think that restricting external properties is really going to far. I will sincerely think twice about using Maven in the future, mainly because of this problem. External property file in command line -- Key: MNG-2046 URL: http://jira.codehaus.org/browse/MNG-2046 Project: Maven 2 Issue Type: Improvement Components: Command Line Affects Versions: 2.0.2 Reporter: Raphaël Corre Priority: Minor Fix For: 2.1.x It would be great to allow the option -propertyfile in the command line, like Ant does to load multi properties. For the moment, it's possible to do 'D, but for a single property. -- 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-2046) External property file in command line
[ http://jira.codehaus.org/browse/MNG-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106074 ] Andris Rauda commented on MNG-2046: --- Luckily, Bamboo guys have resolved my problem by adding more proper way to obtain build number. Still, I believe that Maven should not restrict any features, that other tools have, even if these features seem bad. Otherwise, you might find yourself in a stupid situation, when reasoning with someone about migration from Ant to Maven and discovering, that you actually can't provide the same functionality that Ant does. External property file in command line -- Key: MNG-2046 URL: http://jira.codehaus.org/browse/MNG-2046 Project: Maven 2 Issue Type: Improvement Components: Command Line Affects Versions: 2.0.2 Reporter: Raphaël Corre Priority: Minor Fix For: 2.1.x It would be great to allow the option -propertyfile in the command line, like Ant does to load multi properties. For the moment, it's possible to do 'D, but for a single property. -- 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-1420) Build Fresh and Profile columns are missed in group build definitions page for specific project build definitions
Build Fresh and Profile columns are missed in group build definitions page for specific project build definitions --- Key: CONTINUUM-1420 URL: http://jira.codehaus.org/browse/CONTINUUM-1420 Project: Continuum Issue Type: Bug Reporter: Emmanuel Venisse Fix For: 1.1-beta-3 columns are ok for group build definitions -- 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-1420) Build Fresh and Profile columns are missed in group build definitions page for specific project build definitions
[ http://jira.codehaus.org/browse/CONTINUUM-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1420: Affects Version/s: 1.1-beta-2 Fix Version/s: 1.1-beta-3 Build Fresh and Profile columns are missed in group build definitions page for specific project build definitions --- Key: CONTINUUM-1420 URL: http://jira.codehaus.org/browse/CONTINUUM-1420 Project: Continuum Issue Type: Bug Affects Versions: 1.1-beta-2 Reporter: Emmanuel Venisse Fix For: 1.1-beta-3 columns are ok for group build definitions -- 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-1696) Please sync with locale4j repo
Please sync with locale4j repo -- Key: MAVENUPLOAD-1696 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1696 Project: maven-upload-requests Issue Type: Task Reporter: Tom Cort Please sync with locale4j's repo. locale4j is a library for working with localization data and performing translations. The shell can be found at http://locale4j.sourceforge.net/net.sf.locale4j.sh The repo contains jars for binary, source and javadoc, release 1.1.1. I'm already subscribed to the [EMAIL PROTECTED] list -- 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-1421) Add an admin task to stop properly Continuum
[ http://jira.codehaus.org/browse/CONTINUUM-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1421: Fix Version/s: To Sort Component/s: Core system Add an admin task to stop properly Continuum Key: CONTINUUM-1421 URL: http://jira.codehaus.org/browse/CONTINUUM-1421 Project: Continuum Issue Type: Improvement Components: Core system Reporter: Emmanuel Venisse Fix For: To Sort When a project is building and an admin stop continuum, the actual build result is never marked as stopped. A possible solution would be to planned a shutdown in the web interface via a form. With this action, all sheduler will be stopped and a message will be sent to the admin (page after the submit in the shutdown form). With this message, the admin will know that he can shutdown Continuum properly without non ended build process. -- 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-1421) Add an admin task to stop properly Continuum
Add an admin task to stop properly Continuum Key: CONTINUUM-1421 URL: http://jira.codehaus.org/browse/CONTINUUM-1421 Project: Continuum Issue Type: Improvement Reporter: Emmanuel Venisse Fix For: To Sort When a project is building and an admin stop continuum, the actual build result is never marked as stopped. A possible solution would be to planned a shutdown in the web interface via a form. With this action, all sheduler will be stopped and a message will be sent to the admin (page after the submit in the shutdown form). With this message, the admin will know that he can shutdown Continuum properly without non ended build process. -- 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-1420) Build Fresh and Profile columns are missed in group build definitions page for specific project build definitions
[ http://jira.codehaus.org/browse/CONTINUUM-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse updated CONTINUUM-1420: Component/s: Web - UI Build Fresh and Profile columns are missed in group build definitions page for specific project build definitions --- Key: CONTINUUM-1420 URL: http://jira.codehaus.org/browse/CONTINUUM-1420 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1-beta-2 Reporter: Emmanuel Venisse Fix For: 1.1-beta-3 columns are ok for group build definitions -- 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-1419) Continuum does not accept a Linux file URL with a Bazaar repository.
[ http://jira.codehaus.org/browse/CONTINUUM-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106075 ] Emmanuel Venisse commented on CONTINUUM-1419: - Are you sure it hangs on or only do the checkout without to print something in logs? paste the message that say the URL is incorrect Continuum does not accept a Linux file URL with a Bazaar repository. Key: CONTINUUM-1419 URL: http://jira.codehaus.org/browse/CONTINUUM-1419 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.0.3 Environment: Ubuntu Reporter: James Williams Continuum does not accept a Linux file URL with a Bazaar repository. If you run the exactl text it outputs in the console in another xterm, it executes. But within continuum, it always hangs on bzr check file:///file url In the browser, it indicates that the URL is incorrect despite following the wiki pages precisely. -- 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-1402) Syncing with Perforce on Linux/Unix/Bash fails
[
http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106076
]
Emmanuel Venisse commented on CONTINUUM-1402:
-
What would be the command to use that will be correct? Can you provide a patch
for PLXUTILS-44 ?
INFO: In actual Continuum version, plexus-utils use /bin/bash , the new
plexus-utils code use /bin/sh
Syncing with Perforce on Linux/Unix/Bash fails
--
Key: CONTINUUM-1402
URL: http://jira.codehaus.org/browse/CONTINUUM-1402
Project: Continuum
Issue Type: Bug
Components: Integration - Maven 2, SCM
Affects Versions: 1.1-beta-2
Environment: Bash
Reporter: Sebastian Annies
Priority: Critical
When a client is created it is named:
E.g.{{monospaced}}
sannies-sojus-MavenSCM-\opt\continuum-1.1-beta-3-SNAPSHOT\apps\continuum\webapp\WEB-INF\working-directory\6{{monospaced}}
that is ok, but now comes the sync command and uses following commandline
{{monospaced}}
/bin/bash -c p4 -d
/opt/continuum-1.1-beta-3-SNAPSHOT/apps/continuum/webapp/WEB-INF/working-directory/1
-cbackground-sojus-MavenSCM-\opt\continuum-1.1-beta-3-SNAPSHOT\apps\continuum\webapp\WEB-INF\working-directory\1
sync
{{monospaced}}
The Bash now removes the backslashes in the client name! The result is that
the client is not existent and perforce returns with an error.
I think continuum does everything allright but we need the ticket here to be
reminded to switch to a new plexus-utils or maven-scm if it is fixed there.
The Problem starts in 'PerforceCheckOutCommand':
{{monospaced}}
public static Commandline createCommandLine(
PerforceScmProviderRepository repo, File workingDirectory,
ScmVersion version, String
specname )
{
Commandline command = PerforceScmProvider.createP4Command( repo,
workingDirectory );
{color:red}
command.createArgument().setValue( -c + specname );
{color}
command.createArgument().setValue( sync );
// Use a simple heuristic to determine if we should use the Force flag
// on sync. Forcing sync is a HUGE performance hit but is required in
// rare instances where source is somehow deleted. If the target
// directory is completely empty, assume a force is required. If
// not empty, we assume a previous checkout was already done and a
normal
// sync will suffice.
// SCM-110
String[] files = workingDirectory.list();
if ( files == null || files.length == 0 )
{
// We need to force so checkout to an empty directory will work.
command.createArgument().setValue( -f );
}
// Not sure what to do here. I'm unclear whether we should be
// sync'ing each file individually to the label or just sync the
// entire contents of the workingDir. I'm going to assume the
// latter until the exact semantics are clearer.
if ( version != null StringUtils.isNotEmpty( version.getName() ) )
{
command.createArgument().setValue( @ + version.getName() );
}
return command;
{{monospaced}}
The {{monospaced}}specname {{monospaced}} contains the backslashes and is
these are neither escaped nor quoted! Hmm ... Is that a job that the
CommandLine should handle? I think so!
The next thing I will do is to file an issue at plexus-utils and link the
issues.
--
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-1419) Continuum does not accept a Linux file URL with a Bazaar repository.
[ http://jira.codehaus.org/browse/CONTINUUM-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Williams updated CONTINUUM-1419: -- Attachment: continuum2.png Continuum does not accept a Linux file URL with a Bazaar repository. Key: CONTINUUM-1419 URL: http://jira.codehaus.org/browse/CONTINUUM-1419 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.0.3 Environment: Ubuntu Reporter: James Williams Attachments: continuum.png, continuum2.png Continuum does not accept a Linux file URL with a Bazaar repository. If you run the exactl text it outputs in the console in another xterm, it executes. But within continuum, it always hangs on bzr check file:///file url In the browser, it indicates that the URL is incorrect despite following the wiki pages precisely. -- 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-1419) Continuum does not accept a Linux file URL with a Bazaar repository.
[ http://jira.codehaus.org/browse/CONTINUUM-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Williams updated CONTINUUM-1419: -- Attachment: continuum.png Continuum does not accept a Linux file URL with a Bazaar repository. Key: CONTINUUM-1419 URL: http://jira.codehaus.org/browse/CONTINUUM-1419 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.0.3 Environment: Ubuntu Reporter: James Williams Attachments: continuum.png, continuum2.png Continuum does not accept a Linux file URL with a Bazaar repository. If you run the exactl text it outputs in the console in another xterm, it executes. But within continuum, it always hangs on bzr check file:///file url In the browser, it indicates that the URL is incorrect despite following the wiki pages precisely. -- 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: (MPMD-61) When running build using -f path_to_pom/pom.xml the site is stored in working directory instead of project directory
When running build using -f path_to_pom/pom.xml the site is stored in working directory instead of project directory Key: MPMD-61 URL: http://jira.codehaus.org/browse/MPMD-61 Project: Maven 2.x PMD Plugin Issue Type: Bug Components: PMD Affects Versions: 2.2 Environment: Windows XP, Java 1.5, Maven 2.0.7 Reporter: Peter Hayes Attachments: pmd-multi-module.zip I setup a multi-module build and included the pmd check goal to run during the verify phase. When I execute a build from the top level directory specifying -f path/pom.xml, the plugin creates a target/site/... directory in the current working directory. This directory should be in the project directory and now fails to clean. I have attached a sample project. To reproduce : cd pmd-multi-module mvn -f ./root/pom.xml install Note that after the build there is a target directory in the current working directory with the pmd.html and other files within it. -- 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-1419) Continuum does not accept a Linux file URL with a Bazaar repository.
[ http://jira.codehaus.org/browse/CONTINUUM-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106078 ] James Williams commented on CONTINUUM-1419: --- I checked and it doesn't do a checkout at all. I attached a screenshot of continuum running in console mode and bzr check run in another term. I split it into 2 because I have a dual head setup. Continuum does not accept a Linux file URL with a Bazaar repository. Key: CONTINUUM-1419 URL: http://jira.codehaus.org/browse/CONTINUUM-1419 Project: Continuum Issue Type: Bug Components: SCM Affects Versions: 1.0.3 Environment: Ubuntu Reporter: James Williams Attachments: continuum.png, continuum2.png Continuum does not accept a Linux file URL with a Bazaar repository. If you run the exactl text it outputs in the console in another xterm, it executes. But within continuum, it always hangs on bzr check file:///file url In the browser, it indicates that the URL is incorrect despite following the wiki pages precisely. -- 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-2848) Environment variables in profile activation not working
[
http://jira.codehaus.org/browse/MNG-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106080
]
k commented on MNG-2848:
Has there been any resolution to this issue? I am currently also trying to
access environment variables from within profile (be it within profiles.xml
and pom.xml) with no success. Outside of profile, I can access environment
variables just fine, but within profile, using the environment variable as an
activation property, does not seem to work.
I've been unsuccessful trying to access the variable using the following
methods within profile:
env.FOO
FOO
${env.FOO}
${FOO}
Any information reguarding this issue would be greatly appreciated...
especially since this has been an issue for well over a year now (referring to
http://jira.codehaus.org/browse/MNG-2276 ).
Defining the variable via the commandline interface does work however, as
stated in the link above.
Environment variables in profile activation not working
---
Key: MNG-2848
URL: http://jira.codehaus.org/browse/MNG-2848
Project: Maven 2
Issue Type: Bug
Components: Profiles
Affects Versions: 2.0.4, 2.0.5
Environment: Windows XP Professional, JDK 1.5
Reporter: Muhammad Alsebaey
Fix For: Reviewed Pending Version Assignment
When using an environment variable as a profile activation variable, it
doesnt work, using either env.X or ${env.X} doesnt work.
I found the same issue on the forums unresolved.
http://www.nabble.com/profile-activation-based-on-environment-variables-tf2585492s177.html#a7208580
Basically, the following doesnt work, where FOO is a windows environment
variable (like PATH for example) :
{code:xml}
profile
idharoon-workstation/id
activation
property
nameenv.FOO/name
valuefoo/value
/property
/activation
...
/profile
{code}
--
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] Issue Comment Edited: (MNG-2848) Environment variables in profile activation not working
[
http://jira.codehaus.org/browse/MNG-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106080
]
k edited comment on MNG-2848 at 8/31/07 9:08 AM:
-
Has there been any resolution to this issue? I am currently also trying to
access environment variables from within profile (be it within profiles.xml
and pom.xml) with no success. Outside of profile, I can access environment
variables just fine, but within profile, using the environment variable as an
activation property, does not seem to work.
I've been unsuccessful trying to access the variable using the following
methods within profile:
env.FOO
FOO
${env.FOO}
${FOO}
Any information reguarding this issue would be greatly appreciated...
especially since this has been an issue for well over a year now (referring to
http://jira.codehaus.org/browse/MNG-2276 ).
Defining the variable via the commandline interface does work however, as
stated in the link above.
Btw, my version of maven is 2.0.7
was:
Has there been any resolution to this issue? I am currently also trying to
access environment variables from within profile (be it within profiles.xml
and pom.xml) with no success. Outside of profile, I can access environment
variables just fine, but within profile, using the environment variable as an
activation property, does not seem to work.
I've been unsuccessful trying to access the variable using the following
methods within profile:
env.FOO
FOO
${env.FOO}
${FOO}
Any information reguarding this issue would be greatly appreciated...
especially since this has been an issue for well over a year now (referring to
http://jira.codehaus.org/browse/MNG-2276 ).
Defining the variable via the commandline interface does work however, as
stated in the link above.
Environment variables in profile activation not working
---
Key: MNG-2848
URL: http://jira.codehaus.org/browse/MNG-2848
Project: Maven 2
Issue Type: Bug
Components: Profiles
Affects Versions: 2.0.4, 2.0.5
Environment: Windows XP Professional, JDK 1.5
Reporter: Muhammad Alsebaey
Fix For: Reviewed Pending Version Assignment
When using an environment variable as a profile activation variable, it
doesnt work, using either env.X or ${env.X} doesnt work.
I found the same issue on the forums unresolved.
http://www.nabble.com/profile-activation-based-on-environment-variables-tf2585492s177.html#a7208580
Basically, the following doesnt work, where FOO is a windows environment
variable (like PATH for example) :
{code:xml}
profile
idharoon-workstation/id
activation
property
nameenv.FOO/name
valuefoo/value
/property
/activation
...
/profile
{code}
--
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: (CONTINUUM-1391) Missing Download as text link
[ http://jira.codehaus.org/browse/CONTINUUM-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1391. --- Resolution: Fixed applied. Missing Download as text link Key: CONTINUUM-1391 URL: http://jira.codehaus.org/browse/CONTINUUM-1391 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1-beta-1 Environment: xp Reporter: Dan Tran Assignee: Olivier Lamy Fix For: 1.1-beta-3 Attachments: CONTINUUM-1391 Continuum 1.0.3 provides a link to get a build log in full page which I find it very friendly to view the log. I dont see it in 1.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-482) Saving a proxy connector after adding a new property results to HTTP 500 error
[ http://jira.codehaus.org/browse/MRM-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106087 ] Maria Odea Ching commented on MRM-482: -- This error seems to occur everytime there is modified in the properties of a proxy connector. I've tried to create a new Proxy Connector, added a property then removed it. When I clicked the Save Proxy Connector button, I got the same error again even if I no longer have a property added in the Proxy Connector. Saving a proxy connector after adding a new property results to HTTP 500 error -- Key: MRM-482 URL: http://jira.codehaus.org/browse/MRM-482 Project: Archiva Issue Type: Bug Components: web application Affects Versions: 1.0-beta-1 Reporter: Maria Odea Ching This was the stack trace: HTTP ERROR: 500 [Ljava.lang.String; cannot be cast to java.lang.String RequestURI=/admin/saveProxyConnector.action Caused by: java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String at org.apache.maven.archiva.configuration.io.registry.ConfigurationRegistryWriter.writeProxyConnectorConfiguration(ConfigurationRegistryWriter.java:326) at org.apache.maven.archiva.configuration.io.registry.ConfigurationRegistryWriter.writeConfiguration(ConfigurationRegistryWriter.java:67) at org.apache.maven.archiva.configuration.io.registry.ConfigurationRegistryWriter.write(ConfigurationRegistryWriter.java:31) at org.apache.maven.archiva.configuration.DefaultArchivaConfiguration.save(DefaultArchivaConfiguration.java:183) at org.apache.maven.archiva.web.action.admin.connectors.proxy.ConfigureProxyConnectorAction.saveConfiguration(ConfigureProxyConnectorAction.java:600) at org.apache.maven.archiva.web.action.admin.connectors.proxy.ConfigureProxyConnectorAction.save(ConfigureProxyConnectorAction.java:480) 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:597) at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:364) at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:216) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.apache.maven.archiva.web.interceptor.ConfigurationInterceptor.intercept(ConfigurationInterceptor.java:81) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:103) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:159) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.ParameterFilterInterceptor.intercept(ParameterFilterInterceptor.java:122) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at
[jira] Created: (MASSEMBLY-237) lineEnding ignored in a child project
lineEnding ignored in a child project - Key: MASSEMBLY-237 URL: http://jira.codehaus.org/browse/MASSEMBLY-237 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-1 Environment: Windows Vista Reporter: Todor Todorov Priority: Minor I have a parent project and a child project. The child project builds an assembly composed of text files. fileSet outputDirectorybin/outputDirectory directorysrc/main/bin/directory lineEndingunix/lineEnding includes include*.sh/include /includes /fileSet When I build the assembly from the child project , maven adds unix endings, but when I build it from the parent project, lineEnding is being ignored. -- 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: (CONTINUUM-1041) two defaults on the build definition page
[ http://jira.codehaus.org/browse/CONTINUUM-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1041. --- Assignee: Emmanuel Venisse Resolution: Fixed two defaults on the build definition page - Key: CONTINUUM-1041 URL: http://jira.codehaus.org/browse/CONTINUUM-1041 Project: Continuum Issue Type: Bug Affects Versions: 1.1-alpha-1 Reporter: Brett Porter Assignee: Emmanuel Venisse Fix For: 1.1-beta-3 may be related to CONTINUUM-1040. After completing that, both the group build definition and the new defintion were listed as defaults, while the hardcoded project definition was set to 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: (CONTINUUM-1333) show in project group summary per project also the status counters (as they are shown on the project groups pages)
[ http://jira.codehaus.org/browse/CONTINUUM-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1333. --- Resolution: Fixed I close this issue for now as we have a simple state counter for the group (not by project). We'll can reopen a new issue if we want the solution proposed by Olivier but actually, I don't see the interest to have a counter by project based on build results state. show in project group summary per project also the status counters (as they are shown on the project groups pages) --- Key: CONTINUUM-1333 URL: http://jira.codehaus.org/browse/CONTINUUM-1333 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1-alpha-2 Reporter: tony nys Assignee: Olivier Lamy Priority: Minor Fix For: 1.1-beta-3 Attachments: CONTINUUM-1333, CONTINUUM-1333, screenshot-1.jpg show in project group summary per project also the status counters (as they are shown on the project groups pages) -- 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-228) Try and unable to resolve org.apache.maven.skins:maven-default-skin:jar:RELEASE when another skin is specified
[
http://jira.codehaus.org/browse/MSITE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106092
]
Jennifer Lengel commented on MSITE-228:
---
I am using a local folder for my repository so that maven can not get anything
from central, and i have a super pom with modules that have their own pom as
well. Using my local directories as the only repo maven can access, this work
around does not solve my problem. When I allow maven to go to central
(repo1.maven.org/maven2/), then it does work.
What I need is a work around for my scenario. I am using maven 2.0.5 - or if
this is fixed in a later version that I am not aware of, please let me know.
Thank you,
Jennifer Lengel
Try and unable to resolve
org.apache.maven.skins:maven-default-skin:jar:RELEASE when another skin is
specified
--
Key: MSITE-228
URL: http://jira.codehaus.org/browse/MSITE-228
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-5
Reporter: Stefano Bagnara
1) My project does not use external repositories for dependencies but only
for plugins.
2) For dependencies I have a stage folder that is a legacy structured
local repository I reference this way:
{code}repository
idlocal-james-stage-m1/id
nameLocal James stage repository/name
urlfile://c:/lab/void/projects/server-trunk-modular/stage/url
layoutlegacy/layout
releases
enabledtrue/enabled
checksumPolicyignore/checksumPolicy
/releases
snapshots
enabledtrue/enabled
checksumPolicyignore/checksumPolicy
/snapshots
/repository{code}
3) in my site.xml I have this:
{code}skin
groupIdorg.apache.james/groupId
artifactIdmaven-skin/artifactId
version1.1-SNAPSHOT/version
/skin{code}
4) and in my local stage repository I have the
org.apache.james/poms/maven-skin-1.1-SNAPSHOT.pom and
org.apache.james/jars/maven-skin-1.1-SNAPSHOT.jar files.
If I try to build the project, package it, run tests and everything else it
works, but when I try to build mvn site if fails with this error:
{code}
[DEBUG] maven-default-skin: using locally installed snapshot
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The skin does not exist: Unable to determine the release version
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin \
-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
org.apache.maven.skins:maven-default-skin:jar:RELEASE
[INFO]
[DEBUG] Trace
org.apache.maven.BuildFailureException: The skin does not exist: Unable to
determine the release version
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin \
-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
org.apache.maven.skins:maven-default-skin:jar:RELEASE
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
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)
[jira] Commented: (MSITE-246) path of site.xml not possible to configure in tag siteDirectory
[ http://jira.codehaus.org/browse/MSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106093 ] Jennifer Lengel commented on MSITE-246: --- I have run into this problem. I believe you need to have a directory set up as: D:\omegabox\WEB-INF\src\site\site.xml - From what i understand, maven automatically looks for a site folder, so you don't need the siteDirectory tags or anything. Hope this helps. -Jen path of site.xml not possible to configure in tag siteDirectory - Key: MSITE-246 URL: http://jira.codehaus.org/browse/MSITE-246 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-5 Environment: maven 2.0.7 Reporter: Xavier Marc Priority: Blocker i configure the maven-site-plugin like that : plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.0-beta-5/version configuration siteDirectoryD:\omegabox\WEB-INF\src/siteDirectory /configuration /plugin and my file site.xml is in directory : D:\omegabox\WEB-INF\src\site.xml But when i execute a maven command (mvn site) maven don't find the file site.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-246) path of site.xml not possible to configure in tag siteDirectory
[ http://jira.codehaus.org/browse/MSITE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106096 ] Jennifer Lengel commented on MSITE-246: --- Actually, I may have read your question too fast. If you are trying to specify which folder maven should look for your site.xml in, then I believe there is a bug with it: http://jira.codehaus.org/browse/MSITE-151 If that didn't help, hope this does :) path of site.xml not possible to configure in tag siteDirectory - Key: MSITE-246 URL: http://jira.codehaus.org/browse/MSITE-246 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-5 Environment: maven 2.0.7 Reporter: Xavier Marc Priority: Blocker i configure the maven-site-plugin like that : plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.0-beta-5/version configuration siteDirectoryD:\omegabox\WEB-INF\src/siteDirectory /configuration /plugin and my file site.xml is in directory : D:\omegabox\WEB-INF\src\site.xml But when i execute a maven command (mvn site) maven don't find the file site.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] Created: (MNG-3173) It should be possible to declare transitive dependency exclusions independent of any of the immediately declared dependencies
It should be possible to declare transitive dependency exclusions independent of any of the immediately declared dependencies - Key: MNG-3173 URL: http://jira.codehaus.org/browse/MNG-3173 Project: Maven 2 Issue Type: Improvement Components: POM Affects Versions: 2.0.7 Reporter: Steven Cummings There are situations in projects with many dependencies where a transitive dependency that is desired to be excluded is pulled in by several of the immediate dependencies. In these situations it can be awkward and clumsy to have to add and maintain this particular exclusion in each immediate dependency that introduces it. There should be a way to list exclusions independent of a specific immediate dependency, so that they take effect for all of them wherever the specified artifacts might be introduced transitively. -- 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: (NMAVEN-86) Code sketch for NMaven.Model.Settings support, as well as a non-trivial application thereof in the visual studio addin connect method.
Code sketch for NMaven.Model.Settings support, as well as a non-trivial application thereof in the visual studio addin connect method. --- Key: NMAVEN-86 URL: http://jira.codehaus.org/browse/NMAVEN-86 Project: NMaven Issue Type: Improvement Environment: N/A Reporter: Campbell Boucher-Burnet Priority: Minor Attachments: nmaven-2007-08-30-campbell.patch.zip In the course of using NMaven, it has become evident that a ubiquitous, runtime facility for discovering the local maven repository path (and other settings.xml provided information) is essential. A patch to get started down this road is provided. -- 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-1697) Upload freemarker-2.3.10
Upload freemarker-2.3.10 Key: MAVENUPLOAD-1697 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1697 Project: maven-upload-requests Issue Type: Improvement Reporter: Jochen Wiedmann FreeMarker is a template engine; a generic tool to generate text output based on templates. -- 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: (CONTINUUM-358) User Authentication via LDAP
[ http://jira.codehaus.org/browse/CONTINUUM-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse McConnell closed CONTINUUM-358. - Assignee: Jesse McConnell Resolution: Fixed Fix Version/s: (was: Future) 1.1-beta-3 providing we get continuum updated to use redback-alpha-3 readonly ldap support should exist in 1.1-beta-3 User Authentication via LDAP Key: CONTINUUM-358 URL: http://jira.codehaus.org/browse/CONTINUUM-358 Project: Continuum Issue Type: New Feature Components: Web interface Reporter: Frank Zhao Assignee: Jesse McConnell Fix For: 1.1-beta-3 Please add LDAP support for the user authentication in Continuum user management function. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-1420) Build Fresh and Profile columns are missed in group build definitions page for specific project build definitions
[ http://jira.codehaus.org/browse/CONTINUUM-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated CONTINUUM-1420: Patch Submitted: [Yes] Attachment: CONTINUUM-1420 Patch attached. Adding a link to profile edition with the profile name. Build Fresh and Profile columns are missed in group build definitions page for specific project build definitions --- Key: CONTINUUM-1420 URL: http://jira.codehaus.org/browse/CONTINUUM-1420 Project: Continuum Issue Type: Bug Components: Web - UI Affects Versions: 1.1-beta-2 Reporter: Emmanuel Venisse Assignee: Olivier Lamy Fix For: 1.1-beta-3 Attachments: CONTINUUM-1420 columns are ok for group build definitions -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-280) AIOBE on release:perform
AIOBE on release:perform Key: MRELEASE-280 URL: http://jira.codehaus.org/browse/MRELEASE-280 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-6 Reporter: Milos Kleint got this on current nbm-maven-plugin source at mojo.codehaus.org when doinga release. java.lang.ArrayIndexOutOfBoundsException: 42 at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.translateUrlPath(RewritePomsForReleasePhase.java:249) at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.translateScm(RewritePomsForReleasePhase.java:124) at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.transformScm(RewritePomsForReleasePhase.java:79) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:271) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:180) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:116) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execute(AbstractRewritePomsPhase.java:99) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:127) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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] Commented: (MRELEASE-280) AIOBE on release:perform
[ http://jira.codehaus.org/browse/MRELEASE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106127 ] Milos Kleint commented on MRELEASE-280: --- going back to 2.0-beta-5 worked. AIOBE on release:perform Key: MRELEASE-280 URL: http://jira.codehaus.org/browse/MRELEASE-280 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-6 Reporter: Milos Kleint got this on current nbm-maven-plugin source at mojo.codehaus.org when doinga release. java.lang.ArrayIndexOutOfBoundsException: 42 at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.translateUrlPath(RewritePomsForReleasePhase.java:249) at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.translateScm(RewritePomsForReleasePhase.java:124) at org.apache.maven.shared.release.phase.RewritePomsForReleasePhase.transformScm(RewritePomsForReleasePhase.java:79) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:271) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:180) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:116) at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execute(AbstractRewritePomsPhase.java:99) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:127) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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
