[jira] Commented: (MRELEASE-678) Release with Maven 3.0.3 and Ranges: Referencing Snapshot-Versions
[ http://jira.codehaus.org/browse/MRELEASE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266164#action_266164 ] Christian Bittner commented on MRELEASE-678: Please note, that a "prepare-with-pom" breaks the build, when a snapshot is referenced by a range. For instance: [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:01.764s [INFO] Finished at: Tue May 10 11:16:58 CEST 2011 [INFO] Final Memory: 6M/122M [INFO] maven builder waiting mavenExecutionResult exceptions not empty org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:prepare-with-pom (default-cli) on project RangeProjectB: Can't release project due to non released dependencies : local:XYZ:jar:7.4.4-SNAPSHOT:compile in project 'RangeProjectB' (de.lvm.range.b:RangeProjectB:jar:2.0.5-SNAPSHOT) Of course this doesn't solve the problem. A snapshot must not be referenced in a release context via ranges. Nevertheless: IMHO a "prepare" and a "prepare-with-pom" should work consistently, i.e. a "prepare" must break the build too !!! > Release with Maven 3.0.3 and Ranges: Referencing Snapshot-Versions > -- > > Key: MRELEASE-678 > URL: http://jira.codehaus.org/browse/MRELEASE-678 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.1 > Environment: Maven 3.0.3, java-6-sun 1.6.0_24, RHEL5 >Reporter: Christian Bittner > > In the POM of the to be released project we reference dependencies by range > as follows: > > sample > XYZ > [7.4.0, 7.4.] > > Since the last Version of XYZ is a snapshot the maven-compiler-plugin > classpath in the perform phase references this snapshot (Maven 3.0.3): > [INFO] [DEBUG] (f) classpathElements = > [/opt/mvn/hudson/workspace/RangeB/target/checkout/target/classes, > /opt/mvn/.m2/repository/sample/XYZ/7.4.4-SNAPSHOT/XYZ-7.4.4-SNAPSHOT.jar, > /opt/mvn/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar, > /opt/mvn/.m2/repository/log4j/log4j/1.2.15/log4j-1.2.15.jar, > ... > Snapshots MUST not be referenced in releases. The last released version 7.4.3 > of XYZ must be referenced instead. > Note: We know that this effect is caused by the broken range concept of > maven. Nevertheless the release plugin seems to be the right plugin to report > this, since releasing is senseless when it does not work properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-5090) Maven End Users should be able to control the execution order of plugins without creating a custom Lifecycle and Package Type
[ http://jira.codehaus.org/browse/MNG-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-5090. -- Resolution: Duplicate Assignee: Benjamin Bentmann > Maven End Users should be able to control the execution order of plugins > without creating a custom Lifecycle and Package Type > - > > Key: MNG-5090 > URL: http://jira.codehaus.org/browse/MNG-5090 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 3.0.3 >Reporter: Graham Lea >Assignee: Benjamin Bentmann > > As [confirmed by Benjamin > Bentmann|http://mail-archives.apache.org/mod_mbox/maven-dev/201105.mbox/%3c4dc87d9e.5010...@udo.edu%3E], > Maven end users are currently limited in the control they have over the > execution order of plugins bound to the same build phase unless they author > their own custom Lifecycle and use a custom Package Type. > While Maven is intended to be declarative rather than procedural and to do > most of its work based on sensible defaults, it is a basic requirement of any > build system to allow the end user to control the order in which actions > occur and to do so with a minimum of effort. > It should be possible to configure a plugin, simply and entirely within the > POM, such that it will execute before, or even between, plugins defined by > the lifecycle mappings. -- 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-720) Toolchain is ignored
[
http://jira.codehaus.org/browse/SUREFIRE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266172#action_266172
]
Ronald Muller commented on SUREFIRE-720:
See attached test case. The toolchain configuration is "standard", like
http://maven.apache.org/guides/mini/guide-using-toolchains.html
surefire 2.5 works good, 2.6 - 2.8 fails.
The problem is:
if ( getJvm() != null )
{
getLog().warn( "Toolchains are ignored, 'executable' parameter is set to " +
getJvm() );
}
The JVM is already set, so the toolchain is not used
Kind regards,
Ronald
> Toolchain is ignored
>
>
> Key: SUREFIRE-720
> URL: http://jira.codehaus.org/browse/SUREFIRE-720
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.7, 2.7.1, 2.7.2, 2.8
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: C:\Users\alex\Software\apache-maven-3.0.3\bin\..
> Java version: 1.6.0_19, vendor: Sun Microsystems Inc.
> Java home: C:\Users\alex\Software\jdk1.6.0_19\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>Reporter: Alexander Kitaev
>Assignee: Kristian Rosenvold
>
> The following debug output demonstrates the problem:
> ...
> [INFO] Toolchain in compiler-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22]
> ...
> [INFO] Toolchain in surefire-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22]
> [WARNING] Toolchains are ignored, 'executable' parameter is set to
> C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java
> Forking command line: cmd.exe /X /C
> "C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java -jar
> ...
> Compiler plugin uses proper JDK, while Surefire falls back to default. The
> problem is not reproducible with Surefire 2.6 and 2.5.
--
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-720) Toolchain is ignored
[ http://jira.codehaus.org/browse/SUREFIRE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ronald Muller updated SUREFIRE-720: --- Attachment: SurefireToolchains.zip The test case ... > Toolchain is ignored > > > Key: SUREFIRE-720 > URL: http://jira.codehaus.org/browse/SUREFIRE-720 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.7, 2.7.1, 2.7.2, 2.8 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: C:\Users\alex\Software\apache-maven-3.0.3\bin\.. > Java version: 1.6.0_19, vendor: Sun Microsystems Inc. > Java home: C:\Users\alex\Software\jdk1.6.0_19\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" >Reporter: Alexander Kitaev >Assignee: Kristian Rosenvold > Attachments: SurefireToolchains.zip > > > The following debug output demonstrates the problem: > ... > [INFO] Toolchain in compiler-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > ... > [INFO] Toolchain in surefire-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > [WARNING] Toolchains are ignored, 'executable' parameter is set to > C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java > Forking command line: cmd.exe /X /C > "C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java -jar > ... > Compiler plugin uses proper JDK, while Surefire falls back to default. The > problem is not reproducible with Surefire 2.6 and 2.5. -- 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-546) Cannot supply escapeString for filtering
[
http://jira.codehaus.org/browse/MASSEMBLY-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266194#action_266194
]
Stefan Ferstl commented on MASSEMBLY-546:
-
The same happens when using a properties file for filtering, for example:
*filter.properties*:
{code}
my.property=${user.home}/somedir
{code}
*plugin config*:
{code}
maven-assembly-plugin
true
my-descriptor.xml
${project.build.directory}/assembly/filter.properties
...
}
{code}
*resource file*:
{code}
test=${my.property}
{code}
The resource file in the assembly results in:
{code}
test=C:\Documents and Settings\.../somedir
{code}
instead of
{code}
test=${user.home}/somedir
{code}
The filter.properties file itself does not get filtered. Only the resource file
does. It would be great to have the ability to exclude some variables from
filtering.
> Cannot supply escapeString for filtering
>
>
> Key: MASSEMBLY-546
> URL: http://jira.codehaus.org/browse/MASSEMBLY-546
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
>Affects Versions: 2.2-beta-5
>Reporter: Michael Osipov
>
> I have some txt files filtered in my assembly with true. I'd
> like also some properties tom remain as is and escape filtering. There is no
> option to. In the resources plugin I can set the filter delims + the escape
> string. Something like this is necessary for this plugin too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (SUREFIRE-720) Toolchain is ignored
[ http://jira.codehaus.org/browse/SUREFIRE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold reopened SUREFIRE-720: - > Toolchain is ignored > > > Key: SUREFIRE-720 > URL: http://jira.codehaus.org/browse/SUREFIRE-720 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.7, 2.7.1, 2.7.2, 2.8 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: C:\Users\alex\Software\apache-maven-3.0.3\bin\.. > Java version: 1.6.0_19, vendor: Sun Microsystems Inc. > Java home: C:\Users\alex\Software\jdk1.6.0_19\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" >Reporter: Alexander Kitaev >Assignee: Kristian Rosenvold > Attachments: SurefireToolchains.zip > > > The following debug output demonstrates the problem: > ... > [INFO] Toolchain in compiler-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > ... > [INFO] Toolchain in surefire-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > [WARNING] Toolchains are ignored, 'executable' parameter is set to > C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java > Forking command line: cmd.exe /X /C > "C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java -jar > ... > Compiler plugin uses proper JDK, while Surefire falls back to default. The > problem is not reproducible with Surefire 2.6 and 2.5. -- 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
eclipse - svn - messagebroker integration
Hi All,
I am trying to create a simple BAR file by calling ant through maven. In
this process, i planned to prepare the basic setup in the following way.
• Installed eclipse galileo
• Added the required proxy settings in eclipse.ini
• Installed software updates for svn plugin, connectors and polarin
entries
• Updated http-proxy settings in the subversion file(C:\Documents
and Settings\User\Application Data\Subversion\servers)
• restarted eclipse
After this, while trying to checkout from
SVN('http://wmb-maven-plugin.googlecode.com/svn/trunk') to eclipse, I got
the below errors.
1) svn: PROPFIND of ''/svn/trunk'': 403 Forbidden
(http://wmb-maven-plugin.googlecode.com)
2) Checkout operation for
''http://wmb-maven-plugin.googlecode.com/svn/trunk'' failed. RA layer
request failed svn: OPTIONS of
''http://wmb-maven-plugin.googlecode.com/svn/trunk'': Could not resolve
hostname `wmb-maven-plugin.googlecode.com'': The requested name is valid and
was found in the database, but it does not have the correct associated data
being resolved for.
Not sure what proxy settings i am missing out. Would like to know if someone
successfully integrated maven with either eclipse/wmb toolkit/wmb.
thank you.
--
View this message in context:
http://maven.40175.n5.nabble.com/eclipse-svn-messagebroker-integration-tp4385271p4385271.html
Sent from the Maven - Issues mailing list archive at Nabble.com.
[jira] Closed: (SUREFIRE-720) Toolchain is ignored
[ http://jira.codehaus.org/browse/SUREFIRE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-720. --- Resolution: Fixed Fix Version/s: 2.8.2 Fixed in r1101609. I do not know how to make a proper IT for this, but the test-project was added as part of this commit. > Toolchain is ignored > > > Key: SUREFIRE-720 > URL: http://jira.codehaus.org/browse/SUREFIRE-720 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.7, 2.7.1, 2.7.2, 2.8 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: C:\Users\alex\Software\apache-maven-3.0.3\bin\.. > Java version: 1.6.0_19, vendor: Sun Microsystems Inc. > Java home: C:\Users\alex\Software\jdk1.6.0_19\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" >Reporter: Alexander Kitaev >Assignee: Kristian Rosenvold > Fix For: 2.8.2 > > Attachments: SurefireToolchains.zip > > > The following debug output demonstrates the problem: > ... > [INFO] Toolchain in compiler-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > ... > [INFO] Toolchain in surefire-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > [WARNING] Toolchains are ignored, 'executable' parameter is set to > C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java > Forking command line: cmd.exe /X /C > "C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java -jar > ... > Compiler plugin uses proper JDK, while Surefire falls back to default. The > problem is not reproducible with Surefire 2.6 and 2.5. -- 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: (SUREFIRE-738) Fail on not existing run order.
Fail on not existing run order. --- Key: SUREFIRE-738 URL: http://jira.codehaus.org/browse/SUREFIRE-738 Project: Maven Surefire Issue Type: Improvement Reporter: Stefan Birkner Priority: Minor I want surefire to fail, if I start surefire with a run order, which is not in the set alphabetical, reversealphabetical, random, hourly and fileset. Today I don't get any information, when I start surefire with a wrong run order like alphapetical. -- 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-724) Running individual test cases does not work under JUnit 3.8.2
[
http://jira.codehaus.org/browse/SUREFIRE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266259#action_266259
]
Jesse Glick commented on SUREFIRE-724:
--
JUnit 3 has {{TestSuite.createTest(Class,String)}} which I think is all you
need. This is what Ant 1.8.2 uses. (For >1 method in the same suite, it creates
a new {{TestSuite(String}}} and calls {{addTest}} on each.)
> Running individual test cases does not work under JUnit 3.8.2
> -
>
> Key: SUREFIRE-724
> URL: http://jira.codehaus.org/browse/SUREFIRE-724
> Project: Maven Surefire
> Issue Type: New Feature
> Components: JUnit 3.x support
>Affects Versions: 2.8
> Environment: JDK 6u24, Ubuntu
>Reporter: Jesse Glick
>
> See SUREFIRE-577. After
> {noformat}
> diff --git a/maven-model/pom.xml b/maven-model/pom.xml
> index bc66415..903648a 100644
> --- a/maven-model/pom.xml
> +++ b/maven-model/pom.xml
> @@ -74,6 +74,11 @@ under the License.
>
>
>
> +
> +org.apache.maven.plugins
> +maven-surefire-plugin
> +2.8
> +
>
>
>
> {noformat}
> if I run
> {noformat}
> mvn -f maven-model/pom.xml
> -Dtest=org.apache.maven.model.DependencyTest\#testEqualsIdentity surefire:test
> {noformat}
> I see
> {noformat}
> [INFO] --- maven-surefire-plugin:2.8:test (default-cli) @ maven-model ---
> [INFO] Surefire report directory: .../maven-model/target/surefire-reports
> ---
> T E S T S
> ---
> Running org.apache.maven.model.DependencyTest
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec
> Results :
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> Similarly, in a new quickstart project if I create
> {noformat}
> package test.test196655;
> import junit.framework.TestCase;
> public class AppTest extends TestCase {
> public void test1() {}
> public void test2() {}
> }
> {noformat}
> and run
> {noformat}
> mvn -Dtest=test.test196655.AppTest#test1 test-compile surefire:test
> {noformat}
> both tests are run until I upgrade the JUnit dep from 3.8.1 to 4.8.2.
> By the way the corresponding function works as expected in Ant 1.8.2.
--
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-724) Running individual test cases does not work under JUnit 3.8.2
[
http://jira.codehaus.org/browse/SUREFIRE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266261#action_266261
]
Jesse Glick commented on SUREFIRE-724:
--
Looks like {{JUnit3Provider.invoke}} and
{{JUnit3Reflector.constructTestObject}} are the interesting places in the code.
The former ignores the test method name; the latter calls {{new
TestSuite(Class)}} which adds all detected test methods.
> Running individual test cases does not work under JUnit 3.8.2
> -
>
> Key: SUREFIRE-724
> URL: http://jira.codehaus.org/browse/SUREFIRE-724
> Project: Maven Surefire
> Issue Type: New Feature
> Components: JUnit 3.x support
>Affects Versions: 2.8
> Environment: JDK 6u24, Ubuntu
>Reporter: Jesse Glick
>
> See SUREFIRE-577. After
> {noformat}
> diff --git a/maven-model/pom.xml b/maven-model/pom.xml
> index bc66415..903648a 100644
> --- a/maven-model/pom.xml
> +++ b/maven-model/pom.xml
> @@ -74,6 +74,11 @@ under the License.
>
>
>
> +
> +org.apache.maven.plugins
> +maven-surefire-plugin
> +2.8
> +
>
>
>
> {noformat}
> if I run
> {noformat}
> mvn -f maven-model/pom.xml
> -Dtest=org.apache.maven.model.DependencyTest\#testEqualsIdentity surefire:test
> {noformat}
> I see
> {noformat}
> [INFO] --- maven-surefire-plugin:2.8:test (default-cli) @ maven-model ---
> [INFO] Surefire report directory: .../maven-model/target/surefire-reports
> ---
> T E S T S
> ---
> Running org.apache.maven.model.DependencyTest
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec
> Results :
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> Similarly, in a new quickstart project if I create
> {noformat}
> package test.test196655;
> import junit.framework.TestCase;
> public class AppTest extends TestCase {
> public void test1() {}
> public void test2() {}
> }
> {noformat}
> and run
> {noformat}
> mvn -Dtest=test.test196655.AppTest#test1 test-compile surefire:test
> {noformat}
> both tests are run until I upgrade the JUnit dep from 3.8.1 to 4.8.2.
> By the way the corresponding function works as expected in Ant 1.8.2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WAGON-326) Parent project is always downloaded using lightweight http client
Parent project is always downloaded using lightweight http client - Key: WAGON-326 URL: http://jira.codehaus.org/browse/WAGON-326 Project: Maven Wagon Issue Type: Bug Affects Versions: 1.0-beta-7 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /usr/local/maven Java version: 1.6.0_17, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.18-238.9.1.el5", arch: "amd64", family: "unix" Reporter: Ondrej Svetlik No matter what I do, parent pom is always downloaded using lightweight http client. I tried everything described in this document: http://maven.apache.org/guides/mini/guide-wagon-providers.html but nothing helped. I had to modify my project's pom file to include it's parent in dependencies and remove parent project definition so it could be properly downloaded using httpclient. Then everything works fine with the original pom file and other downloads are using httpclient. I am using httpclient because lightweight ignores my encrypted passwords in settings.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: (MNGSITE-138) Need to document how to get correct classpaths for ant mojo plugins
Need to document how to get correct classpaths for ant mojo plugins --- Key: MNGSITE-138 URL: http://jira.codehaus.org/browse/MNGSITE-138 Project: Maven Project Web Site Issue Type: Bug Reporter: Kenneth Flynn Priority: Critical The documentation here: http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html is really good for getting you started a couple of exceptions. Some of the configuration options in *.mojos.xml are not fully listed, including the parameter, needed to get classpaths correct inside of the ant script. If you fail to set that, you get very strange classpaths (just the target/classes directory) with no other sign of error. If you're familiar with Java Mojo development, I suspect this is obvious, but as a developer coming to this and trying to convert a giant chunk of antrun code into a plugin to achieve reuse, I had to find information on this in a completely different place (the Java mojo stuff), which took me quite a bit of time. I'd recommend adding a brief section on this parameter, with the table of what is in scope copied from the Java mojo section, or at least put a link to that saying "go read this first." There is no documentation on this issue re: ant mojos anywhere that I can find, including stackoverflow, etc. -- 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-159) Support a pattern to generate the release tag
[ http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266311#action_266311 ] Laksiri Dasun commented on MRELEASE-159: Hi Dave , could you please tell me what should i write in tagNameformat order to get only the releseVersion as the tag. > Support a pattern to generate the release tag > - > > Key: MRELEASE-159 > URL: http://jira.codehaus.org/browse/MRELEASE-159 > Project: Maven 2.x Release Plugin > Issue Type: New Feature > Components: prepare >Affects Versions: 2.0-beta-4 >Reporter: Joerg Schaible > Fix For: 2.2 > > Attachments: MRELEASE-159-PATCH-2-0.patch, > MRELEASE-159-PATCH-update.diff.gz, MRELEASE-159-PATCH.diff.gz, > release-manager(updated).patch, release-manager-patch.patch > > > The release-plugin uses currently the pattern "-" to > create the version tag. A configuration element would be fine to support > different requirements for release tags (in our case "v_", since > with svn the module is already part of the path). -- 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: (MRELEASE-159) Support a pattern to generate the release tag
[ http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266311#action_266311 ] Laksiri Dasun edited comment on MRELEASE-159 at 5/11/11 12:29 AM: -- Hi Dave , could you please tell me what should i write in tagNameformat inorder to get only the releseVersion as the tag. eg: "1.0.0" was (Author: dasun): Hi Dave , could you please tell me what should i write in tagNameformat order to get only the releseVersion as the tag. > Support a pattern to generate the release tag > - > > Key: MRELEASE-159 > URL: http://jira.codehaus.org/browse/MRELEASE-159 > Project: Maven 2.x Release Plugin > Issue Type: New Feature > Components: prepare >Affects Versions: 2.0-beta-4 >Reporter: Joerg Schaible > Fix For: 2.2 > > Attachments: MRELEASE-159-PATCH-2-0.patch, > MRELEASE-159-PATCH-update.diff.gz, MRELEASE-159-PATCH.diff.gz, > release-manager(updated).patch, release-manager-patch.patch > > > The release-plugin uses currently the pattern "-" to > create the version tag. A configuration element would be fine to support > different requirements for release tags (in our case "v_", since > with svn the module is already part of the path). -- 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
