[jira] Issue Comment Edited: (MNG-3638) Ability to evaluate expressions involving collections
[
http://jira.codehaus.org/browse/MNG-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149684#action_149684
]
bentmann edited comment on MNG-3638 at 10/3/08 5:51 AM:
-
bq. If someone can come up with a solid, deterministic rule for how this can be
done, I can implement it.
Does it need more than an index operator to allow users to specify which
collection element they refer to? I mean, the POM is XML, XML is a sequence of
elements so all collections should in fact be lists that can be accessed via a
zero-based index.
The brackets that Java uses for array indexing are forbidden in URI paths but
there are still other available delimiter characters. So, how about something
like one of these:
{noformat}
project/build/resources/0/directory
project/build/resources,0/directory
project/build/resources(0)/directory
{noformat}
was (Author: bentmann):
bq. If someone can come up with a solid, deterministic rule for how this
can be done, I can implement it.
Does it need more than an index operator to allow users to specify which
collection element they refer to? I mean, the POM is XML, XML is a sequence of
elements so all collections should in fact be lists that can be accessed via a
zero-based index.
The brackets that Java uses for array indexing are forbidden in URI paths but
there are still other available delimiter characters. So, how about something
like one of these:
{noformat}
project/build/resources,0/directory
project/build/resources(0)/directory
{noformat}
Ability to evaluate expressions involving collections
-
Key: MNG-3638
URL: http://jira.codehaus.org/browse/MNG-3638
Project: Maven 2
Issue Type: New Feature
Components: General
Affects Versions: 2.0.9
Environment: Windows XP Professional SP 2
Reporter: Matthew Tordoff
Fix For: 3.x
The following property is not resolved by Maven:
${project.build.resources.resource.directory}
It follows the notation described to access any property within the POM, is
there an alternative property that can be used to reference the resource
directory?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-258) Remove EOL in the docbook sink
Remove EOL in the docbook sink -- Key: DOXIA-258 URL: http://jira.codehaus.org/browse/DOXIA-258 Project: Maven Doxia Issue Type: Improvement Components: Module - Docbook Simple Affects Versions: 1.0-beta-1 Reporter: Vincent Siveton Using PrintWriter instead of LineBreaker -- 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: (MCHANGES-106) the generated jira-result.xml contains no jira-items
[ http://jira.codehaus.org/browse/MCHANGES-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149784#action_149784 ] darren hartford commented on MCHANGES-106: -- ok, I'm not crazy Running into exact same problem, Maven 2.0.9, Fedora 9, Maven Changes Plugin 2.0, and JIRA 3.12.2-#300. going to the link from the debug shows a list off issues, but jira-results.xml only shows the rss/channel block and no issues. force/verify maven changes plugin 2.0 pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changes-plugin/artifactId version2.0/version /plugin /plugins /pluginManagement Running with -X, it's using: doxia 1.0-alpha-9 plexux-utils-1.4.5 plexus-velocity 1.1.7 velocity 1.4 the generated jira-result.xml contains no jira-items Key: MCHANGES-106 URL: http://jira.codehaus.org/browse/MCHANGES-106 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira-report Affects Versions: 2.0-beta-3 Environment: windows maven-2.0.8 jira Professional Edition, Version: 3.11-#288 Reporter: Rene Boers Priority: Critical Attachments: jira-report.html, jira-report.log, jira-results.xml, jira-results.xml, pom.xml, screenshot-1.jpg when i run the maven site or mvn changes:jira-report the resulting jira-reports doesnot contain jira-issues it only contains the link to the searchrequest. This results in an empty jira-report. I have included the jira-reports.xml and the logging from the mvn changes:jira report. When open the jira-reports.xml in firefox i do have a page with the request jira-issues available. In explorer i just get the representation of the xml file. Any suggestions why no jira-report is generated. -- 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: (DOXIA-258) Remove EOL in the docbook sink
[ http://jira.codehaus.org/browse/DOXIA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIA-258: -- Attachment: DOXIA-258.patch Here is the patch. I propose also to move LineBreaker class from core to latex module Remove EOL in the docbook sink -- Key: DOXIA-258 URL: http://jira.codehaus.org/browse/DOXIA-258 Project: Maven Doxia Issue Type: Improvement Components: Module - Docbook Simple Affects Versions: 1.0-beta-1 Reporter: Vincent Siveton Attachments: DOXIA-258.patch Using PrintWriter instead of LineBreaker -- 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-2230) Upload JFreeChart 1.0.11
Upload JFreeChart 1.0.11 Key: MAVENUPLOAD-2230 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2230 Project: Maven Upload Requests Issue Type: Wish Reporter: Martin Höller Attachments: jcommon-1.0.14-bundle.jar, jfreechart-1.0.11-bundle.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: (MASSEMBLY-355) I get duplicate files in my -jar-with-dependencies.jar
[ http://jira.codehaus.org/browse/MASSEMBLY-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149802#action_149802 ] Alvin Thompson commented on MASSEMBLY-355: -- this is not the same problem as MASSEMBLY-285. even if 285 fixes the symptom, it doesn't address the root cause. IMHO this should be reopened. I get duplicate files in my -jar-with-dependencies.jar Key: MASSEMBLY-355 URL: http://jira.codehaus.org/browse/MASSEMBLY-355 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-2 Environment: mvn --version Maven version: 2.0.9 Java version: 1.5.0_13 OS: OSX 10.5.5 Reporter: Bjørn Magnus Mathisen Assignee: John Casey Fix For: 2.2-beta-3 Attachments: testProj.zip, testProj.zip I get duplicate files in my -jar-with-dependencies.jar build with mvn package, then try to unzip the mentioned jar file, it asks if you want to replace, this also hampers any signing of the jar file.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MASSEMBLY-358) where should I get the 2.2-beta-3 or snapshot of the maven-assembly-plugin ?
[ http://jira.codehaus.org/browse/MASSEMBLY-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier closed MASSEMBLY-358. --- Resolution: Fixed The project roadmap shows what needs to be done before the next release: http://jira.codehaus.org/browse/MASSEMBLY?report=com.atlassian.jira.plugin.system.project:roadmap-panel where should I get the 2.2-beta-3 or snapshot of the maven-assembly-plugin ? Key: MASSEMBLY-358 URL: http://jira.codehaus.org/browse/MASSEMBLY-358 Project: Maven 2.x Assembly Plugin Issue Type: New Feature Affects Versions: 2.2-beta-2 Environment: unix Reporter: Michael Meng Assignee: Wendy Smoak Priority: Critical I got a error of appxml attribute is required while using the format ear. in MASSEMBLY-345, it says fixed in 2.2-beta-3 How could I ge the 2.2-beta-3 or the snapshot ? Thanks -- 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: (MANTRUN-95) Plugin classpath problem in multi module maven project
[
http://jira.codehaus.org/browse/MANTRUN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149812#action_149812
]
Ceki Gulcu commented on MANTRUN-95:
---
It seems that if a antrun-plugin is declared in say module M0, then the
dependency declaration
within the antrun-plugin are ignored nut only if building from the top-level
directory. Building
from the module itself, that is from TOP_LEVEL/M0/ folder works fine.
I have tested this with Maven 2.0.8., 2.0.9 and 2.1.0-M1 as well as
antrun-plugin and 1.1 and 1.2.
Plugin classpath problem in multi module maven project
--
Key: MANTRUN-95
URL: http://jira.codehaus.org/browse/MANTRUN-95
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Environment: WindowsXP Pro
jdk1.5.0_11
MAVEN 2.0.9
Reporter: Alexandre GIGLEUX
Attachments: ProblemMavenPluginClasspath.zip
We have a pom.xml with modules :
modules
module./Module1/module
module./Module2/module
/modules
In Module1 we use the define dependencies.
In Module2 we also define dependencies for maven-antrun-plugin with other
dependency.
Problem when we display echo message=plugin classpath: ${plugin_classpath}
/, in Module2 we have the classpath of the Module1.
The only workaround is to add specific dependency of Module2, in Module1
(for the maven-antrun-plugin plugin).
It looks like the plugin classpath is not updated for each Module.
--
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: (MINVOKER-70) invoker:install does not properly handle versioned dependencies
invoker:install does not properly handle versioned dependencies --- Key: MINVOKER-70 URL: http://jira.codehaus.org/browse/MINVOKER-70 Project: Maven 2.x Invoker Plugin Issue Type: Bug Affects Versions: 1.3 Reporter: Jared Roberts Priority: Critical The fix for MINVOKER-64 introduced a regression. Previously, only the artifact under test was installed to the IT local repository. The other dependencies were then resolved from remote repositories. In 1.3, the other dependencies are pulled from the actual local repository. It appears that the resolution of uniquely versioned dependencies is different in the two flows because the 1.2.1 flow downloaded both the uniquely versioned jar and the non-unique jar but the 1.3 flow only installs the uniquely versioned jar. My build now fails because it cannot find the non-uniquely versioned jar to run my integration tests. -- 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: (MASSEMBLY-314) Multiple inclusion of dependencies in binary assembly
[
http://jira.codehaus.org/browse/MASSEMBLY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149816#action_149816
]
Paul Gier commented on MASSEMBLY-314:
-
I just ran into this issue, and I can confirm that it can be fixed using the
same {{archiverConfig}} configuration described in MASSEMBLY-285.
Can we change the default behavior of the assembly plugin? It seems like it
makes more sense to not allow duplicates by default. Especially since, as
Rainer described, the dir format will not include duplicates and you can end
up with different contents for dir vs. zip for example.
Multiple inclusion of dependencies in binary assembly
-
Key: MASSEMBLY-314
URL: http://jira.codehaus.org/browse/MASSEMBLY-314
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Environment: all
Reporter: Thorsten Möller
Fix For: 2.2-beta-3
Hello,
today I tried to upgrade the Maven assembly plugin from 2.2-beta-1 to
2.2-beta-2. However, I noticed that for my project which consists of multiple
modules the resulting binary assembly now contains dependency JAR files
multiple times. The assembly descriptor contains the following excerpt (with
changed module names):
moduleSets
moduleSet
includes
include${pom.groupId}:a/include
include${pom.groupId}:b/include
include${pom.groupId}:c/include
/includes
binaries
includeDependenciestrue/includeDependencies
unpackfalse/unpack
outputDirectory/lib/outputDirectory
/binaries
/moduleSet
/moduleSets
The projects a, b, c have several dependencies, whereby some of those
dependencies refer to identical artifacts (derived from a parent POM), e.g.,
commons-logging. The resulting ZIP and TAR.GZ assembly files then contain
those dependencies multiple times (in the lib folder) with equal names! Im
not sure if this is a bug or a feature and I might have missed something.
I rolled back to version 2.2-beta-1 and I could reproduce the issue.
2.2-beta-1 works as expected, i.e., all files exist only once.
Regards,
Thorsten
--
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-3769) Excluding transitive dependencies does not work
[
http://jira.codehaus.org/browse/MNG-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luke w patterson updated MNG-3769:
--
Attachment: MNG-3769-debugging-info.zip
With the pom.xml from attachment 1, I captured some info that might be useful
for anyone debugging this.
See MNG-3769-debugging-info.zip
step 0:
created empty local repo directory /2.0.9-repo
created empty local repo directory /2.1.0-M1-repo
step 1: using maven 2.0.9 pointing to /2.0.9-repo, ran
org.apache.maven.plugins:maven-dependency-plugin:2.0:tree, goal completed
console capture is in step1-2.0.9-tree.txt
content listing of /2.0.9-repo is in step1-2.0.9-repo-contents.txt
step 2: using maven 2.1.0-M1 pointing to /2.1.0-M1-repo, ran
org.apache.maven.plugins:maven-dependency-plugin:2.0:tree, goal completed
console capture is in step2-2.1.0-M1-tree.txt
content listing of /2.1.0-M1-repo is in step2-2.1.0-M1-repo-contents.txt
step 3: using maven 2.1.0-M1 pointing to /2.0.9-repo, ran
org.apache.maven.plugins:maven-dependency-plugin:2.0:tree, goal failed
console capture is in step3-2.1.0-M1-tree.txt
content listing of /2.0.9-repo is in step3-2.0.9-repo-contents.txt
Excluding transitive dependencies does not work
---
Key: MNG-3769
URL: http://jira.codehaus.org/browse/MNG-3769
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.1.0-M1
Reporter: Dirk Olmes
Priority: Blocker
Attachments: MNG-3769-debugging-info.zip, pom.xml
I'm trying to exclude transitive dependencies of a dependency. This works
fine with 2.0.9, however it does not work with 2.1.0-M1.
Run {{mvn dependency:tree}} on the attached pom.xml with 2.0.9 and note how
there is no javax.activation in the tree. Re-run with 2.1.0-M1 and note how
javax.activation shows up in the dependencies tree.
--
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-3769) Excluding transitive dependencies does not work
[
http://jira.codehaus.org/browse/MNG-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
luke w patterson updated MNG-3769:
--
Attachment: MNG-3769-debugging-info-2.zip
Oops, last attachment didn't have debugging turned on during dependency:tree.
This attachment does.
Excluding transitive dependencies does not work
---
Key: MNG-3769
URL: http://jira.codehaus.org/browse/MNG-3769
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.1.0-M1
Reporter: Dirk Olmes
Priority: Blocker
Attachments: MNG-3769-debugging-info-2.zip,
MNG-3769-debugging-info.zip, pom.xml
I'm trying to exclude transitive dependencies of a dependency. This works
fine with 2.0.9, however it does not work with 2.1.0-M1.
Run {{mvn dependency:tree}} on the attached pom.xml with 2.0.9 and note how
there is no javax.activation in the tree. Re-run with 2.1.0-M1 and note how
javax.activation shows up in the dependencies tree.
--
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: (MINVOKER-70) invoker:install does not properly handle versioned dependencies
[ http://jira.codehaus.org/browse/MINVOKER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149825#action_149825 ] Benjamin Bentmann commented on MINVOKER-70: --- Could you give some more details, e.g. the listing of JAR files resolved for your problematic dependency in the staging repo when using plugin version 1.2.1 and 1.3? I currently just don't get enough understanding of the problem from your description to come up with a test or fix. invoker:install does not properly handle versioned dependencies --- Key: MINVOKER-70 URL: http://jira.codehaus.org/browse/MINVOKER-70 Project: Maven 2.x Invoker Plugin Issue Type: Bug Affects Versions: 1.3 Reporter: Jared Roberts Priority: Critical The fix for MINVOKER-64 introduced a regression. Previously, only the artifact under test was installed to the IT local repository. The other dependencies were then resolved from remote repositories. In 1.3, the other dependencies are pulled from the actual local repository. It appears that the resolution of uniquely versioned dependencies is different in the two flows because the 1.2.1 flow downloaded both the uniquely versioned jar and the non-unique jar but the 1.3 flow only installs the uniquely versioned jar. My build now fails because it cannot find the non-uniquely versioned jar to run my integration tests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-259) Source code snippets are not indented automatically
Source code snippets are not indented automatically
---
Key: DOXIA-259
URL: http://jira.codehaus.org/browse/DOXIA-259
Project: Maven Doxia
Issue Type: Bug
Components: Module - Apt
Affects Versions: 1.0-alpha-9
Reporter: Michael Osipov
Attachments: unindented.png
I tried the following in apt:
{noformat}
* sdfs
%{snippet|id=resolveLocale|file=java-core/src/main/java/net/fckeditor/localization/LocaleResolver.java}
On every request it will
passed the current HttpServletRequest instance. It resolves the user
locale according to the underlying system or returns null if it can't
resolve the locale.
[]
{noformat}
As you can see from the png attachment. The source box is not indented as it
done by default if the source mode is used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3525) Settings.xml allowing mirror definitions inside profiles
[ http://jira.codehaus.org/browse/MNG-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149827#action_149827 ] David J. M. Karlsen commented on MNG-3525: -- This would most definately be useful for ppl going in and out of different environments. Can it be resceduled for 2.1.x? Settings.xml allowing mirror definitions inside profiles Key: MNG-3525 URL: http://jira.codehaus.org/browse/MNG-3525 Project: Maven 2 Issue Type: Improvement Components: Profiles Affects Versions: 2.0.9 Environment: N/A Reporter: Paul Grove Fix For: 3.0-alpha-2 I currently use Maven in 2 places 1. At work 2. Not at work At work we have a repository manager thus we have mirror properties in the settings.xml for the whole teams global settings. We also have a defined a number of repositories in our work profile so we can mirror these to different repo's managed by Archiva. Now when I work from home I have to comment out the mirror definitions and activate a home profile which does not define any repos so Maven just goes out to the WWW as normal. So the pain is having to comment out and un-comment the mirror settings every time I go from work to home and visa-versa. Can we not have the option to add mirrors inside profiles? -- 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: (MNGSITE-69) Link to Ant Tasks project website is broken
[ http://jira.codehaus.org/browse/MNGSITE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MNGSITE-69. -- Resolution: Duplicate Link to Ant Tasks project website is broken --- Key: MNGSITE-69 URL: http://jira.codehaus.org/browse/MNGSITE-69 Project: Maven 2 Project Web Site Issue Type: Bug Environment: Any Reporter: Rick Mann Priority: Critical In the lower-left area of the maven website is a set of links for Project Documentation, the first of which is the Ant Task. This link is broken. Every year or so, I come back to the maven project, and there always seems to be missing documentation/broken links. http://maven.apache.org/ant-tasks/index.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1538) xml-apis-1.2.01.jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149832#action_149832 ] Dennis Lundberg commented on MAVENUPLOAD-1538: -- This issue is about uploading xml-apis:xml-apis:1.2.01 to the central repo. It's not just an issue for ICEFaces. Other projects suffer from this as well. Also from what I understand. using xerces:* artifacts is the old way and using xml-apis:* is the new and preferred way. So in order to provide a solid upgrade path for users of the XML APIs we should add xml-apis:xml-apis:1.2.01 to the central repo. If we do that, people will not have to change groupIds and they won't have to worry about getting multiple instances of the APIs into the classpath. xml-apis-1.2.01.jar --- Key: MAVENUPLOAD-1538 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1538 Project: Maven Upload Requests Issue Type: Task Reporter: Michael Böckling Assignee: Carlos Sanchez Attachments: pom.xml, xml-apis-1.2.01.jar An older version of xml-apis. Needed by ICEFaces-1.5.3 which will follow later on. POM is partially copied from http://mirrors.ibiblio.org/pub/mirrors/maven2/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRESOURCES-24) Force overwrite resources defined in profiles
[ http://jira.codehaus.org/browse/MRESOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149833#action_149833 ] Olivier Lamy commented on MRESOURCES-24: As I'd like to do a resources plugin soon, can you provide a test case or test with the currrent ? Thanks ! Force overwrite resources defined in profiles - Key: MRESOURCES-24 URL: http://jira.codehaus.org/browse/MRESOURCES-24 Project: Maven 2.x Resources Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Kees de Kooter Assignee: Olivier Lamy Fix For: 2.3 I am using profiles to package for different environments. The profile typically defines a couple of properties files with db and log settings. The resource plugin only overwrites files that are changed, so the profile specific resources with the same name are ignored and the wrong resources are packaged. I could do a clean first, but that seems a bit of a crude approach. I would prefer to have a property like overwrite=true on a resource. -- 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: (MRESOURCES-24) Force overwrite resources defined in profiles
[ http://jira.codehaus.org/browse/MRESOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149838#action_149838 ] Kees de Kooter commented on MRESOURCES-24: -- I will try to test asap Olivier. Thanks sofar. Force overwrite resources defined in profiles - Key: MRESOURCES-24 URL: http://jira.codehaus.org/browse/MRESOURCES-24 Project: Maven 2.x Resources Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Kees de Kooter Assignee: Olivier Lamy Fix For: 2.3 I am using profiles to package for different environments. The profile typically defines a couple of properties files with db and log settings. The resource plugin only overwrites files that are changed, so the profile specific resources with the same name are ignored and the wrong resources are packaged. I could do a clean first, but that seems a bit of a crude approach. I would prefer to have a property like overwrite=true on a resource. -- 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: (MRESOURCES-24) Force overwrite resources defined in profiles
[ http://jira.codehaus.org/browse/MRESOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149833#action_149833 ] olamy edited comment on MRESOURCES-24 at 10/3/08 3:31 PM: - As I'd like to do a resources plugin release soon, can you provide a test case or test with the currrent ? Thanks ! was (Author: olamy): As I'd like to do a resources plugin soon, can you provide a test case or test with the currrent ? Thanks ! Force overwrite resources defined in profiles - Key: MRESOURCES-24 URL: http://jira.codehaus.org/browse/MRESOURCES-24 Project: Maven 2.x Resources Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Kees de Kooter Assignee: Olivier Lamy Fix For: 2.3 I am using profiles to package for different environments. The profile typically defines a couple of properties files with db and log settings. The resource plugin only overwrites files that are changed, so the profile specific resources with the same name are ignored and the wrong resources are packaged. I could do a clean first, but that seems a bit of a crude approach. I would prefer to have a property like overwrite=true on a resource. -- 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: (MRESOURCES-24) Force overwrite resources defined in profiles
[ http://jira.codehaus.org/browse/MRESOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149843#action_149843 ] Olivier Lamy commented on MRESOURCES-24: I have added an [it|https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-resources-plugin/src/it/profile-override/] which looks similar to your use case. Can you verify ? Force overwrite resources defined in profiles - Key: MRESOURCES-24 URL: http://jira.codehaus.org/browse/MRESOURCES-24 Project: Maven 2.x Resources Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Kees de Kooter Assignee: Olivier Lamy Fix For: 2.3 I am using profiles to package for different environments. The profile typically defines a couple of properties files with db and log settings. The resource plugin only overwrites files that are changed, so the profile specific resources with the same name are ignored and the wrong resources are packaged. I could do a clean first, but that seems a bit of a crude approach. I would prefer to have a property like overwrite=true on a resource. -- 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] Work started: (MANTRUN-68) Use ant-1.7.1
[ http://jira.codehaus.org/browse/MANTRUN-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MANTRUN-68 started by Barrie Treloar. Use ant-1.7.1 - Key: MANTRUN-68 URL: http://jira.codehaus.org/browse/MANTRUN-68 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Affects Versions: 1.1 Environment: xp, linux Reporter: Dan Tran Assignee: Barrie Treloar Fix For: 1.3 Attachments: MANTRUN-68-maven-antrun-plugin.patch with out this upgrade, i will need to exec ant 1.7.1 to use its new features like abily to do delete,move, etc using filelist -- 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: (MANTRUN-68) Use ant-1.7.1
[ http://jira.codehaus.org/browse/MANTRUN-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrie Treloar closed MANTRUN-68. - Resolution: Fixed Upgraded to ant-1.7.1 Added integration tests using echoxml (1.7 feature only) Also upgraded to plexus-utils 1.5.6 which has FileUtils.contentEquals() Use ant-1.7.1 - Key: MANTRUN-68 URL: http://jira.codehaus.org/browse/MANTRUN-68 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Affects Versions: 1.1 Environment: xp, linux Reporter: Dan Tran Assignee: Barrie Treloar Fix For: 1.3 Attachments: MANTRUN-68-maven-antrun-plugin.patch with out this upgrade, i will need to exec ant 1.7.1 to use its new features like abily to do delete,move, etc using filelist -- 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-3762) Relocation not working for plugins
[
http://jira.codehaus.org/browse/MNG-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149857#action_149857
]
luke w patterson commented on MNG-3762:
---
Just to make sure the relocation metadata was correct, I modified your example
from
plugins
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version7.0.0pre3/version
/plugin
/plugins
to
dependencies
dependency
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version7.0.0pre3/version
/dependency
/dependencies
and it downloaded fine.
Relocation not working for plugins
--
Key: MNG-3762
URL: http://jira.codehaus.org/browse/MNG-3762
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.9
Environment: Maven version: 2.0.9
Java version: 1.5.0_13
OS name: mac os x version: 10.5.4 arch: i386 Family: unix
Reporter: Wendy Smoak
As discussed on the user list, the relocation pom for the Jetty plugin does
not seem to work correctly.
See: http://www.nabble.com/Does-relocation-work-for-plugins--td19618624.html
To reproduce, create a project from the webapp archetype, and introduce the
Jetty plugin:
{noformat}
build
...
plugins
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version7.0.0pre3/version
/plugin
/plugins
{noformat}
Attempting to build the project results in an error:
{noformat}
$ mvn install
[INFO] Scanning for projects...
[INFO]
[INFO] Building mywebapp Maven Webapp
[INFO]task-segment: [install]
[INFO]
Downloading:
http://repo1.maven.org/maven2/org/mortbay/jetty/maven-jetty-plugin/7.0.0pre3/maven-jetty-plugin-7.0.0pre3.jar
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] A required plugin was not found: Plugin could not be found -
check that the goal name is correct: Unable to download the artifact
from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.mortbay.jetty
-DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3
-Dpackaging=maven-plugin -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.mortbay.jetty
-DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3
-Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Mon Sep 22 19:02:01 MST 2008
[INFO] Final Memory: 3M/7M
[INFO]
{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: (MANTRUN-68) Use ant-1.7.1
[ http://jira.codehaus.org/browse/MANTRUN-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149861#action_149861 ] Dan Tran commented on MANTRUN-68: - bravo let's release it :-) Use ant-1.7.1 - Key: MANTRUN-68 URL: http://jira.codehaus.org/browse/MANTRUN-68 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Affects Versions: 1.1 Environment: xp, linux Reporter: Dan Tran Assignee: Barrie Treloar Fix For: 1.3 Attachments: MANTRUN-68-maven-antrun-plugin.patch with out this upgrade, i will need to exec ant 1.7.1 to use its new features like abily to do delete,move, etc using filelist -- 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-3525) Settings.xml allowing mirror definitions inside profiles
[ http://jira.codehaus.org/browse/MNG-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149865#action_149865 ] Brian Fox commented on MNG-3525: 2.1 can't handle a model change yet so most likely no for 2.x Settings.xml allowing mirror definitions inside profiles Key: MNG-3525 URL: http://jira.codehaus.org/browse/MNG-3525 Project: Maven 2 Issue Type: Improvement Components: Profiles Affects Versions: 2.0.9 Environment: N/A Reporter: Paul Grove Fix For: 3.0-alpha-2 I currently use Maven in 2 places 1. At work 2. Not at work At work we have a repository manager thus we have mirror properties in the settings.xml for the whole teams global settings. We also have a defined a number of repositories in our work profile so we can mirror these to different repo's managed by Archiva. Now when I work from home I have to comment out the mirror definitions and activate a home profile which does not define any repos so Maven just goes out to the WWW as normal. So the pain is having to comment out and un-comment the mirror settings every time I go from work to home and visa-versa. Can we not have the option to add mirrors inside profiles? -- 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-2231) org.eclipse.help base pom file has invalid dependency
org.eclipse.help base pom file has invalid dependency - Key: MAVENUPLOAD-2231 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2231 Project: Maven Upload Requests Issue Type: Bug Reporter: Matt Holcomb I apologize if this is not the correct place to log this issue. This is in the http://repo1.maven.org/eclipse/ repository. The org.eclipse.help.base has an invalid dependency -- it requires org.eclipse.core runtime 3.3.0 which does not exist in the repository. Two levels deeper requires org.eclipse.core runtime 3.3.100-v200705030 which does exist in the repository. Here is the dependency tree: org.eclipse.help base 3.3.0-v20070606 org.eclipse.core runtime 3.3.0 org.eclipse help 3.3.0-v20070524 org.eclipse.core runtime 3.3.100-v20070530 I assume that this should be fixed, or maybe I am not aware of the reason for this? I could not find this version in any of the recent eclipse installations. (I only searched the versions I already had locally). -- 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: (MANTRUN-68) Use ant-1.7.1
[ http://jira.codehaus.org/browse/MANTRUN-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149866#action_149866 ] Barrie Treloar commented on MANTRUN-68: --- I'm in the process of working out how to do that :) Bare with me, i'm making a mess of it so far. Probably a couple of days. Use ant-1.7.1 - Key: MANTRUN-68 URL: http://jira.codehaus.org/browse/MANTRUN-68 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Affects Versions: 1.1 Environment: xp, linux Reporter: Dan Tran Assignee: Barrie Treloar Fix For: 1.3 Attachments: MANTRUN-68-maven-antrun-plugin.patch with out this upgrade, i will need to exec ant 1.7.1 to use its new features like abily to do delete,move, etc using filelist -- 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: (MANTRUN-68) Use ant-1.7.1
[ http://jira.codehaus.org/browse/MANTRUN-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149868#action_149868 ] Dan Tran commented on MANTRUN-68: - Could you doc/blog your experience going apache maven release process? This is very handy for any new commiter what would like to sponsor a release Use ant-1.7.1 - Key: MANTRUN-68 URL: http://jira.codehaus.org/browse/MANTRUN-68 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Affects Versions: 1.1 Environment: xp, linux Reporter: Dan Tran Assignee: Barrie Treloar Fix For: 1.3 Attachments: MANTRUN-68-maven-antrun-plugin.patch with out this upgrade, i will need to exec ant 1.7.1 to use its new features like abily to do delete,move, etc using filelist -- 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
