[jira] Updated: (MDEP-214) Accompany outputFilterFile with possibility of of definining used property name.
[ http://jira.codehaus.org/browse/MDEP-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ivanov updated MDEP-214: --- Attachment: filter_property_name.patch Patch against 2.1 is attached > Accompany outputFilterFile with possibility of of definining used property > name. > > > Key: MDEP-214 > URL: http://jira.codehaus.org/browse/MDEP-214 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement > Components: build-classpath >Affects Versions: 2.1 >Reporter: Tuomas Kiviaho >Assignee: Brian Fox >Priority: Minor > Attachments: filter_property_name.patch > > > Currently filter format is hardcoded as 'classpath=x'. assembly plugin > bundles files and filter together so each classpath property file > (unix/windows/..) requires separate assembly plugin definition for each > classpath variant. By exposing an 'outputFilterName' parameter, this extra > step would be removed. Instead of above one could have classpath.unix=x, > classpath.windows=y. One step further would be the possibility of > appending these into same file, but only if that wouldn't require yet another > parameter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MDEP-260) \ causes an exception
[ http://jira.codehaus.org/browse/MDEP-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ivanov updated MDEP-260: --- Attachment: file_separator.patch A fix for correct regexp escaping > \ causes an exception > > > Key: MDEP-260 > URL: http://jira.codehaus.org/browse/MDEP-260 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: build-classpath >Affects Versions: 2.1 >Reporter: Sergei Ivanov >Assignee: Brian Fox > Attachments: file_separator.patch > > > If I specify the following property in the plugin configuration: > \ > then the plugin crashes with an exception because a regex parser fails > internally. > It appears that the property needs to be escaped like this: > \\ > The plugin should take care of escaping the property itself. -- 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: (MDEP-260) \ causes an exception
[ http://jira.codehaus.org/browse/MDEP-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218809#action_218809 ] Sergei Ivanov commented on MDEP-260: Damn, even Jira cannot escape strings properly. There was a double backslash in the second example. Anyway, the problem is due to regular expression replacement string not being properly escaped, and backslash has a special meaning there (see javadoc on java.lang.String#replaceAll() ). Please consider the attached patch (against 2.1 release) that resolves the problem. > \ causes an exception > > > Key: MDEP-260 > URL: http://jira.codehaus.org/browse/MDEP-260 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: build-classpath >Affects Versions: 2.1 >Reporter: Sergei Ivanov >Assignee: Brian Fox > Attachments: file_separator.patch > > > If I specify the following property in the plugin configuration: > \ > then the plugin crashes with an exception because a regex parser fails > internally. > It appears that the property needs to be escaped like this: > \\ > The plugin should take care of escaping the property itself. -- 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: (MDEP-260) \ causes an exception
\ causes an exception Key: MDEP-260 URL: http://jira.codehaus.org/browse/MDEP-260 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: build-classpath Affects Versions: 2.1 Reporter: Sergei Ivanov Assignee: Brian Fox If I specify the following property in the plugin configuration: \ then the plugin crashes with an exception because a regex parser fails internally. It appears that the property needs to be escaped like this: \\ The plugin should take care of escaping the property itself. -- 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-459) releaseProfiles has no effect without passing profiles in the command line
[
http://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218807#action_218807
]
Karl M. Davis commented on MRELEASE-459:
I actually had to use the following to get things to work:
{{mvn release:perform -Darguments="-PmyProfileToActivate"}}
I think this is because I'm also using the {{-DconnectionUrl=...}} option and
don't have any profiles defined in my {{settings.xml}}.
> releaseProfiles has no effect without passing profiles in the command line
> ---
>
> Key: MRELEASE-459
> URL: http://jira.codehaus.org/browse/MRELEASE-459
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
>Affects Versions: 2.0-beta-8, 2.0-beta-9
>Reporter: Andreas Christoforides
> Attachments: patch.txt
>
>
> The releaseProfiles parameter on the perform goal is not taken into
> consideration when no other profiles are passed in the command line. In other
> words, the current code only uses the value of the parameter if you have
> additional profiles passed in.
> Example:
> mvn release:perform -P someProfile (uses releaseProfiles value)
> mvn release:perform (does NOT use releaseProfiles value)
> The plugin should use the parameter even if no other profiles are passed. It
> should actually encourage release profiles configured in your POM as opposed
> to arbitrary profiles passed in the command line.
> I have included a patch that uses the releaseProfiles parameter regardless of
> any profiles passed in the command line.
--
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: (MDEP-214) Accompany outputFilterFile with possibility of of definining used property name.
[ http://jira.codehaus.org/browse/MDEP-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218805#action_218805 ] Sergei Ivanov commented on MDEP-214: I faced exactly the same problem today. I needed to generate two classpath properties: one for unix environments, one for windows. In my project, there is only a single assembly execution that produces a multi-platform binary distro. If I had an option of specifying two separate classpath properties, I would be able to build a multi-platform assembly in a single pass. > Accompany outputFilterFile with possibility of of definining used property > name. > > > Key: MDEP-214 > URL: http://jira.codehaus.org/browse/MDEP-214 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement > Components: build-classpath >Affects Versions: 2.1 >Reporter: Tuomas Kiviaho >Assignee: Brian Fox >Priority: Minor > > Currently filter format is hardcoded as 'classpath=x'. assembly plugin > bundles files and filter together so each classpath property file > (unix/windows/..) requires separate assembly plugin definition for each > classpath variant. By exposing an 'outputFilterName' parameter, this extra > step would be removed. Instead of above one could have classpath.unix=x, > classpath.windows=y. One step further would be the possibility of > appending these into same file, but only if that wouldn't require yet another > parameter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MWAR-223) war:exploded with war dependency doesn't copy the src/main/resources to WEB-INF/classses
war:exploded with war dependency doesn't copy the src/main/resources to WEB-INF/classses Key: MWAR-223 URL: http://jira.codehaus.org/browse/MWAR-223 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1-beta-1 Environment: Windows XP Pro SP3 Java HotSpot(TM) Client VM (build 1.5.0_16-b02, mixed mode, sharing) Reporter: Nicolas COSME The war:exploded goal on a webapp project that depends on another war failed to copy the src/main/resources content (or other resources defined in the pom) to the WEB-INF/classes target. Use case : 1- Create a wepapp projet with toto.xml into src/main/resources 2- Launch mvn war:exploded, in ./target/mywebapp/WEB-INF/classes, the file 'toto.xml' is present. 3- Add a dependency on another war project containing java resources or not, and launch the previous goal, the file 'toto.xml' is not present. Quick fix; Force the copy using the 'webResource' property in your pom. org.apache.maven.plugins maven-war-plugin 2.1-alpha-1 src/main/resources WEB-INF/classes -- 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: (MDEPLOY-43) Deploy plugin does not consider artifact type when deploying snapshots
[ http://jira.codehaus.org/browse/MDEPLOY-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218759#action_218759 ] Brill Pappin commented on MDEPLOY-43: - This issue was submitted in 2006 and marked "Critical"... but it's not even assigned! I don't hold out much hope that the developers of this plugin are paying attention. I'd guess the way to get it fixed is for someone to submit a patch and hope that there is someone around who can apply it. > Deploy plugin does not consider artifact type when deploying snapshots > -- > > Key: MDEPLOY-43 > URL: http://jira.codehaus.org/browse/MDEPLOY-43 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug >Affects Versions: 2.2.1 > Environment: all environments >Reporter: Brill Pappin >Priority: Critical > > A single artifact with multiple components is not handled properly. > Deploying a single snapshot artifact that has multiple components such as a > native component with an so/dll file and a matching lib file results in two > different id's while only the last id is recorded in the meta data. > Of course, this means that the first file can not be resolve. > The deploy plugin should take the file type into account when deploying the > artifact so that multiple components of an artifact have the same snapshot > id. > To test the issue, use the native-maven-plugin > (http://mojo.codehaus.org/maven-native/native-maven-plugin/index.html) to > deploy an artifact as a snapshot version. > Once deployed inspect the repository; You should find an so/dll and a lib > with two different snapshot ids and the maven-metadata.xml will contain the > id of the last file that was actually copied (in this case the lib 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] Commented: (SCM-547) Release on Windows, of a multi-module project, using msysgit, throws a StringIndexOutOfBoundsException
[
http://jira.codehaus.org/browse/SCM-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218750#action_218750
]
Ricky Clarkson commented on SCM-547:
At the point the exception occurs, I printed out the contents of baseDirs, and
found that the first was lowercase and the rest were uppercase. I changed the
population of baseDirs to use .toLowerCase(Locale.ENGLISH) and got further, but
found another problem: C:\uk-org-netvu\common\pom.xml is outside repository,
which I think I can solve in maven-scm-plugin.
I'd like to change the component of this ticket to maven-release-plugin but I
can't see a way of editing that.
> Release on Windows, of a multi-module project, using msysgit, throws a
> StringIndexOutOfBoundsException
> --
>
> Key: SCM-547
> URL: http://jira.codehaus.org/browse/SCM-547
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
>Affects Versions: 1.3
> Environment: Windows XP 32-bit, msysgit 1.6.5.1-preview20091022,
> maven 2.2.1
>Reporter: Ricky Clarkson
>
> Install msysgit with the default settings. Launch Git Bash.
> git clone http://github.com/rickyclarkson/maven-git-testcase.git
> cd maven-git-testcase
> mvn release:prepare
> The following is the output:
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Unnamed - org.test:maven-git-testcase-parent:pom:1.0-SNAPSHOT
> [INFO] Unnamed - org.test:maven-git-testcase-child:jar:1.0-SNAPSHOT
> [INFO] Searching repository for plugin with prefix: 'release'.
> [INFO]
>
> [INFO] Building Unnamed - org.test:maven-git-testcase-parent:pom:1.0-SNAPSHOT
> [INFO]task-segment: [release:prepare] (aggregator-style)
> [INFO]
>
> [INFO] [release:prepare {execution: default-cli}]
> [INFO] Verifying that there are no local modifications...
> [INFO] Executing: cmd.exe /X /C "git status"
> [INFO] Working directory: c:\Documents and Settings\Craig\maven-git-testcase
> [INFO] nothing added to commit but untracked files present (use "git add" to
> track)
> [INFO] Checking dependencies and plugins for snapshots ...
> What is the release version for "Unnamed -
> org.test:maven-git-testcase-parent:pom:1.0-SNAPSHOT"?
> (org.test:maven-git-testcase-parent) 1.0: :
> What is the release version for "Unnamed -
> org.test:maven-git-testcase-child:jar:1.0-SNAPSHOT"?
> (org.test:maven-git-testcase-child) 1.0: :
> What is SCM release tag or label for "Unnamed -
> org.test:maven-git-testcase-parent:pom:1.0-SNAPSHOT"?
> (org.test:maven-git-testcase-parent) maven-git-t
> estcase-parent-1.0: :
> What is the new development version for "Unnamed -
> org.test:maven-git-testcase-parent:pom:1.0-SNAPSHOT"?
> (org.test:maven-git-testcase-parent) 1.1-SNAP
> SHOT: :
> What is the new development version for "Unnamed -
> org.test:maven-git-testcase-child:jar:1.0-SNAPSHOT"?
> (org.test:maven-git-testcase-child) 1.1-SNAPSH
> OT: :
> [INFO] Transforming 'Unnamed -
> org.test:maven-git-testcase-parent:pom:1.0-SNAPSHOT'...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] String index out of range: -1
> [INFO]
>
> [INFO] Trace
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1937)
> at
> org.apache.maven.shared.release.util.ReleaseUtil.getCommonBasedir(ReleaseUtil.java:206)
> at
> org.apache.maven.shared.release.util.ReleaseUtil.getCommonBasedir(ReleaseUtil.java:177)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:303)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:208)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:114)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execute(AbstractRewritePomsPhase.java:97)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
[jira] Created: (MAVENUPLOAD-2770) OSGi 4.2.0 Enterprise API
OSGi 4.2.0 Enterprise API - Key: MAVENUPLOAD-2770 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2770 Project: Maven Upload Requests Issue Type: Wish Reporter: Holger Hoffstätte Attachments: org.osgi.enterprise-4.2.0.jar This is the recently released OSGi 4.2.0 Enterprise API in bundle form. I have manually created sha1 checksums for all artifacts; the pom is maven-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] Commented: (MRESOURCES-110) escapeString is broken - break filtered output
[
http://jira.codehaus.org/browse/MRESOURCES-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218746#action_218746
]
Andreas Höhmann commented on MRESOURCES-110:
I can reproduce the bug too.
In my case this results in broken utf-8 encoding string :-)
ist keine g\u00FCltige Zahl
will be "transformed" to
ist keine g\00FCltige Zahl
> escapeString is broken - break filtered output
> --
>
> Key: MRESOURCES-110
> URL: http://jira.codehaus.org/browse/MRESOURCES-110
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
>Affects Versions: 2.4, 2.4.1
> Environment: Maven 2.0.9, WinXP
>Reporter: Marco Rothe
>Priority: Critical
>
> If the escapeString parameter is specified in plugin configuration this will
> break the filtered output.
> For example the configuration
>
>maven-resources-plugin
>2.4.1
>
> !
>
>
> an file to filter (an XML file)
>
>
>
>Why are my !\${\}\! static.content broken if the escapeString
> occure ?!?
>Content with replacement: ${replaceThis} !
>Content with escaped replacement: Do not !${replaceThis}
> !
>
> and a property
>
> I am the replacement
>
> from pom or profile.xml
> result in
>
>
>
>Why are my !${\}\!static.content broken if the escapeString
> occure ?!
>Content with replacement: I am the replacement !/broken-tag>
>Content with escaped replacement: Do not ${replaceThis}
> !/broken-tag>
>
> Note the broken comment and tags!
> If using Resources-Plugin 2.3 the output is like expected:
>
>
>
>Why are my !\${\}\! static.content broken if the escapeString
> occure ?!?
>Content with replacement: I am the replacement !
>Content with escaped replacement: Do not ${replaceThis}
> !
>
> Got even worse when using a complex escape string like
> static (I know it's a silly example ;)). The
> result is
>
>
>
>Why are my !\${\}\! staticcontent broken if the escapeSring
> occure ?!?
>Content with replacement: I am the replacement !
>Content with escapedreplacement: Do not !I am the replacement
> !
>
> Note the missing characters all over the file ... :-/
> So the actual state of the escapeString feature is unpredictable and nearly
> useless.
--
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: (MSHADE-78) Possibility to rename classes, e.g. to define a name prefix, to avoid classes with same names
Possibility to rename classes, e.g. to define a name prefix, to avoid classes with same names - Key: MSHADE-78 URL: http://jira.codehaus.org/browse/MSHADE-78 Project: Maven 2.x Shade Plugin Issue Type: New Feature Reporter: Tim Ducheyne Priority: Minor It would be nice if there was an option to, next to relocating the classes, also rename them, for example by giving them a certain prefix. Suppose you bundle a third-party lib in your own lib. Suppose a project uses your lib and also uses the third-party lib. If you then start looking up classes in your IDE, 2 classes with the same name (but different package) will pop-up. Renaming them would avoid this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-613) Wrong number of JUnit4 tests when running in parallel
[ http://jira.codehaus.org/browse/SUREFIRE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218735#action_218735 ] Mag Hoehme commented on SUREFIRE-613: - Hi Kristian, thank you for your quick response. The problem seems to be with the surefire plugin 2.5 and only arises when the tests run in parallel. The number of tests is fine when parallel execution is switched off. The tests are correctly annotated. I attached a small demo project that shows the problem. > Wrong number of JUnit4 tests when running in parallel > - > > Key: SUREFIRE-613 > URL: http://jira.codehaus.org/browse/SUREFIRE-613 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.5 > Environment: Cygwin > Maven 2.0.9 > Maven Surefire plugin 2.5 > JUnit 4.8.1 >Reporter: Mag Hoehme > Attachments: junit4-test.tar.gz > > > I have a test class with three test methods, out of which two fail. When > running sequentially, I get the following output, which is correct in my > opinion: > === > Tests run: 3, Failures: 2, Errors 0, Skipped 0, > Results: > Failed tests: >a(...) >b(...) > Tests run: 3, Failures: 2, Errors: 0, Skipped: 0 > === > Then I switch to parallel execution: > === pom.xml === > >org.apache.maven.plugins >maven-surefire-plugin >2.5. > > classes > > > === > This gives me the following output from the same test class: > === > Tests run: 2, Failures: 2, Errors, 0, Skipped: 0 ... > Results : > Failed tests: >a(...) >b(...) > Tests run: 2, Failures: 2, Errors: 0, Skipped: 0 > === > The same problem occurs with "methods" and > "tests". When running a bunch of tests, the reported > number of tests is lower than the actual number of tests. > Am I missing something, or is this a bug? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SUREFIRE-613) Wrong number of JUnit4 tests when running in parallel
[ http://jira.codehaus.org/browse/SUREFIRE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mag Hoehme updated SUREFIRE-613: Attachment: junit4-test.tar.gz Demo project illustrating the wrong number of executed tests for parallel execution. > Wrong number of JUnit4 tests when running in parallel > - > > Key: SUREFIRE-613 > URL: http://jira.codehaus.org/browse/SUREFIRE-613 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.x support >Affects Versions: 2.5 > Environment: Cygwin > Maven 2.0.9 > Maven Surefire plugin 2.5 > JUnit 4.8.1 >Reporter: Mag Hoehme > Attachments: junit4-test.tar.gz > > > I have a test class with three test methods, out of which two fail. When > running sequentially, I get the following output, which is correct in my > opinion: > === > Tests run: 3, Failures: 2, Errors 0, Skipped 0, > Results: > Failed tests: >a(...) >b(...) > Tests run: 3, Failures: 2, Errors: 0, Skipped: 0 > === > Then I switch to parallel execution: > === pom.xml === > >org.apache.maven.plugins >maven-surefire-plugin >2.5. > > classes > > > === > This gives me the following output from the same test class: > === > Tests run: 2, Failures: 2, Errors, 0, Skipped: 0 ... > Results : > Failed tests: >a(...) >b(...) > Tests run: 2, Failures: 2, Errors: 0, Skipped: 0 > === > The same problem occurs with "methods" and > "tests". When running a bunch of tests, the reported > number of tests is lower than the actual number of tests. > Am I missing something, or is this a bug? -- 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
