[jira] (SUREFIRE-811) remote-testing
[ https://jira.codehaus.org/browse/SUREFIRE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293550#comment-293550 ] Henning Gross commented on SUREFIRE-811: We have decided not to write a patch for surefire as this would have meant to much effort / cost. Instead we have build a separate plugin to achieve our goals. It may be interesting for people coming here searching for a solution for a similar problem. You can find documentation, anonymous access to code and binaries/public maven repo here: https://evolvis.org/plugins/mediawiki/wiki/mvn-remote-test/index.php/Main_Page. If you want to add/change something, feel free to submit patches/join as a committer. > remote-testing > -- > > Key: SUREFIRE-811 > URL: https://jira.codehaus.org/browse/SUREFIRE-811 > Project: Maven Surefire > Issue Type: New Feature > Components: Maven Failsafe Plugin >Reporter: Henning Gross > > Add the possibility to copy the target folder to remote machine and run > integration-tests there. Copy back the results and handle them as if they > would have been ran locally. > I would volounteer to submit a patch for this feature if theres a chance it > would be accepted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SCM-668) Unable to get revision number with Git and SVN 1.7
Laurent Prévost created SCM-668:
---
Summary: Unable to get revision number with Git and SVN 1.7
Key: SCM-668
URL: https://jira.codehaus.org/browse/SCM-668
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-api
Affects Versions: 1.7
Environment: Mac OS X Snow Leopard
Maven 2 and 3
Maven SCM 1.7 and previous ones
Multi modules project
Reporter: Laurent Prévost
I am unable to use the plugin buildnumber-maven-plugin to get the revision
number with Git and SVN. After some investigations, I realized that the plugin
used the Maven-SCM-API and their providers.
The command issued by the plugin is
{code}
/bin/sh -c cd /tmp/temp/mytestingrepo && git rev-parse --verify --short=7 HEAD
{code}
I run this command directly in a shell with the following error
{code}
fatal: Not a git repository (or any of the parent directories): .git
{code}
When I modify the command like the following one, it works perfectly
{code}
/bin/sh -c "cd /tmp/temp/mytestingrepo && git rev-parse --verify --short=7 HEAD"
{code}
It seems that the command is not executed correctly on my environment where the
{code}
/bin/sh -c "cd /tmp/temp/mytestingrepo
{code}
is executed and afterwards the command
{code}
git rev-parse --verify --short=7 HEAD
{code}
is done in the current directory. In the case of SVN 1.7 and Git, the .svn or
.git are not located in subdirectories where the second command is executed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTRUN-172) Properties passed to Maven as -D don't get passed to invocations when a profile sets the same property
[
https://jira.codehaus.org/browse/MANTRUN-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293555#comment-293555
]
Ondrej Zizka commented on MANTRUN-172:
--
Workaround: In a dummy profile, define a property like this:
{code}
ts.ipv6.dummy.node1
node1
${node1}
{code}
Ant plugin will buy that.
> Properties passed to Maven as -D don't get passed to invocations when a
> profile sets the same property
>
>
> Key: MANTRUN-172
> URL: https://jira.codehaus.org/browse/MANTRUN-172
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Derek Lewis
> Attachments: maven-antrun-plugin-bug.zip
>
>
> When I invoke Maven as follows:
> mvn package -Dmy.test.property="from commandline" -Ptest-profile
> Setting my.test.property on the command line, I expect to see the following
> output from the testcase:
> [echo] pom.xml: ptest = from commandline
> [echo] pom.xml: my.test.property = from commandline
> [echo] build.xml: ptest = from commandline
> [echo] build.xml: my.test.property = from commandline
> But instead I see:
> [echo] pom.xml: ptest = from commandline
> [echo] pom.xml: my.test.property = from commandline
> [echo] build.xml: ptest = from commandline
> [echo] build.xml: my.test.property = from profile
> It looks like the task is causing properties set on the command line to
> not be inherited.
> When run without -Ptest-profile, the expected output is seen. The comments
> on MANTRUN-121 would seem to imply that properties set on the commandline
> should always be passed to sub builds, regardless of the value of the
> inheritAll property.
> I've tested with a profile in the pom as well as in settings.xml, and the
> same behavior is observed regardless of where the profile is, so long as it
> is activated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MENFORCER-124) Rule-scoped fail property
[ https://jira.codehaus.org/browse/MENFORCER-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293592#comment-293592 ] Mirko Friedenhagen commented on MENFORCER-124: -- I just posted a message to the developer list with this suggestion: - Add an optional qualifier per rule which differentiates between INFO, WARNING and ERROR (same as the loglevels) and - Make the rules log with this level on the console and - Make the build optionally fail only if there were violations with log level ERROR. For backward compatibility when no qualifier is given, rules will default to ERROR. > Rule-scoped fail property > - > > Key: MENFORCER-124 > URL: https://jira.codehaus.org/browse/MENFORCER-124 > Project: Maven 2.x Enforcer Plugin > Issue Type: New Feature >Affects Versions: 1.0.1 >Reporter: marko asplund > > The fail property is plugin configuration scoped. It would be useful to be > able to set it separately per rule. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHADE-105) Classes processed by the relocator still have references to the original classes in their constant pools
[ https://jira.codehaus.org/browse/MSHADE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293593#comment-293593 ] Andreas Veithen commented on MSHADE-105: Can somebody please review this issue? We have this problem with Apache Axiom, and if the issue is not fixed, we will have to release Axiom with a patched version of the shade plugin. > Classes processed by the relocator still have references to the original > classes in their constant pools > > > Key: MSHADE-105 > URL: https://jira.codehaus.org/browse/MSHADE-105 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.4 >Reporter: Andreas Veithen >Priority: Minor > Attachments: constant-pool.patch, javap2.txt, javap.txt > > > DefaultShader uses the ClassWriter(ClassReader, int) constructor instead of > ClassWriter(int). According to the ASM Javadoc, this has the following > effects: > "- The constant pool from the original class is copied as is in the new > class, which saves time. New constant pool entries will be added at the end > if necessary, but unused constant pool entries won't be removed. > - Methods that are not transformed are copied as is in the new class, > directly from the original class bytecode (i.e. without emitting visit events > for all the method instructions), which saves a lot of time. Untransformed > methods are detected by the fact that the ClassReader receives MethodVisitor > objects that come from a ClassWriter (and not from a custom ClassAdapter or > any other ClassVisitor instance)." > The second item is actually not applicable in the case of DefaultShader > because the entire class needs to be transformed anyway. On the other hand, > the first item implies that the constant pool of the transformed class will > still have references to the original classes. This can be seen from the > attached "javap.txt" file (produced by javap on a class relocated by > maven-shade-plugin): the relocation adds new entries at the end of the > constant pool, but the original entries are still present. > Since the original entries are no longer referenced anywhere in the class, > this has no consequences at runtime. However, some tools such as Felix' > maven-bundle-plugin use the constant pool to determine the dependencies of a > class. The effect is that if such a shaded JAR is embedded into a bundle > using maven-bundle-plugin, it will generate spurious Import-Package > instructions referring to the original package names. An example of this is > described in AXIS2-5145. > The solution to this problem is simply not to pass the ClassReader object to > the ClassWriter constructor. With this change, the constant pool is properly > cleaned up (see the attached "javap2.txt" file). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-542) JUnit 4.4 tests skipped for a failed assumption are not reported as "Skipped"
[
https://jira.codehaus.org/browse/SUREFIRE-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293596#comment-293596
]
Karl M. Davis commented on SUREFIRE-542:
Please note that, in order for JUnit assumptions to work as intended, your
tests must be JUnit 4-style, e.g. not extend from {{TestCase}} and instead use
{{@Test}} annotations. This is obvious in retrospect, but I just blew an hour
or so figuring it out. Hope it saves someone else time.
> JUnit 4.4 tests skipped for a failed assumption are not reported as "Skipped"
> -
>
> Key: SUREFIRE-542
> URL: https://jira.codehaus.org/browse/SUREFIRE-542
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
>Affects Versions: 2.4.3
> Environment: 64 bit Ubuntu 8.10, OpenJDK 6
>Reporter: Karl M. Davis
>Assignee: Kristian Rosenvold
>Priority: Minor
> Fix For: 2.7.2
>
> Attachments: SUREFIRE-542.patch
>
>
> Junit 4.4 has support for ignoring tests at runtime via code like the
> following:
> {{Assume.assumeTrue(testsShouldBeRun());}}
> When running tests under Surefire that fail their assumptions, the tests are
> reported as successful-- not ignored as they ought to be. The javadoc for
> the Assume class is here: [http://junit.org/apidocs/org/junit/Assume.html].
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
Laurent Malvert created MRESOURCES-160:
--
Summary: NPE when copy-resources set to use the default
as aspecified by documentation
Key: MRESOURCES-160
URL: https://jira.codehaus.org/browse/MRESOURCES-160
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Components: copy
Affects Versions: 2.5
Environment: Windows 7 64 bits
Java 1.6.0_31 x64
maven 3.0.4
Reporter: Laurent Malvert
Attachments: error.log, resources-npe.tar.gz
h2. Context and Issue
When using the {{maven-resources-plugin}} to copy a resource to a custom
directory using the {{copy-resources}} goal, it triggers an NPE without any
additional information when the {{}} element is not specified:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
(copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
NullPointerException -> [Help 1]
{noformat}
However, the documentation at: http://maven.apache.org/pom.html#Resources
clearly states:
{quote}
directory: This element's value defines where the resources are to be found.
The default directory for a build is ${basedir}/src/main/resources.
{quote}
Specifying it explictly with this value works as intended.
_(Not sure if relevant to maven-resources-plugin or the MSHARED resources
component?)_
h2. Test Case
Or at leat a project to reproduce.
See the attached project for a working test case, which uses this configuration:
{code}
org.apache.maven.plugins
maven-resources-plugin
2.5
copy-resources
validate
copy-resources
${basedir}/resources
**/somefile.xml
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
[
https://jira.codehaus.org/browse/MRESOURCES-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293614#comment-293614
]
Laurent Malvert commented on MRESOURCES-160:
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong.
However, it shouldn't really fail with an NPE without giving any helpful
information.
> NPE when copy-resources set to use the default as
> aspecified by documentation
> ---
>
> Key: MRESOURCES-160
> URL: https://jira.codehaus.org/browse/MRESOURCES-160
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.5
> Environment: Windows 7 64 bits
> Java 1.6.0_31 x64
> maven 3.0.4
>Reporter: Laurent Malvert
> Attachments: error.log, resources-npe.tar.gz
>
>
> h2. Context and Issue
> When using the {{maven-resources-plugin}} to copy a resource to a custom
> directory using the {{copy-resources}} goal, it triggers an NPE without any
> additional information when the {{}} element is not
> specified:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
> (copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
> NullPointerException -> [Help 1]
> {noformat}
> However, the documentation at: http://maven.apache.org/pom.html#Resources
> clearly states:
> {quote}
> directory: This element's value defines where the resources are to be found.
> The default directory for a build is ${basedir}/src/main/resources.
> {quote}
> Specifying it explictly with this value works as intended.
> _(Not sure if relevant to maven-resources-plugin or the MSHARED resources
> component?)_
> h2. Test Case
> Or at leat a project to reproduce.
> See the attached project for a working test case, which uses this
> configuration:
> {code}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
> copy-resources
> validate
>
> copy-resources
>
>
>
> ${basedir}/resources
>
>
>
>
>
>
> **/somefile.xml
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
[
https://jira.codehaus.org/browse/MRESOURCES-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293614#comment-293614
]
Laurent Malvert edited comment on MRESOURCES-160 at 3/7/12 7:49 PM:
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
{quote}
[...] The default directory for a build is ${basedir}/src/main/resources.
{quote}
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
was (Author: laurent.malvert):
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
.bq "[...] The default directory for a build is ${basedir}/src/main/resources."
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
> NPE when copy-resources set to use the default as
> aspecified by documentation
> ---
>
> Key: MRESOURCES-160
> URL: https://jira.codehaus.org/browse/MRESOURCES-160
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.5
> Environment: Windows 7 64 bits
> Java 1.6.0_31 x64
> maven 3.0.4
>Reporter: Laurent Malvert
> Attachments: error.log, resources-npe.tar.gz
>
>
> h2. Context and Issue
> When using the {{maven-resources-plugin}} to copy a resource to a custom
> directory using the {{copy-resources}} goal, it triggers an NPE without any
> additional information when the {{}} element is not
> specified:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
> (copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
> NullPointerException -> [Help 1]
> {noformat}
> However, the documentation at: http://maven.apache.org/pom.html#Resources
> clearly states:
> {quote}
> directory: This element's value defines where the resources are to be found.
> The default directory for a build is ${basedir}/src/main/resources.
> {quote}
> Specifying it explictly with this value works as intended.
> _(Not sure if relevant to maven-resources-plugin or the MSHARED resources
> component?)_
> h2. Test Case
> Or at leat a project to reproduce.
> See the attached project for a working test case, which uses this
> configuration:
> {code}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
> copy-resources
> validate
>
> copy-resources
>
>
>
> ${basedir}/resources
>
>
>
>
>
>
> **/somefile.xml
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
[
https://jira.codehaus.org/browse/MRESOURCES-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293614#comment-293614
]
Laurent Malvert edited comment on MRESOURCES-160 at 3/7/12 7:50 PM:
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
{quote}
[...] The default directory for a build is {{$\{basedir\}/src/main/resources}}.
{quote}
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
was (Author: laurent.malvert):
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
{quote}
[...] The default directory for a build is ${basedir}/src/main/resources.
{quote}
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
> NPE when copy-resources set to use the default as
> aspecified by documentation
> ---
>
> Key: MRESOURCES-160
> URL: https://jira.codehaus.org/browse/MRESOURCES-160
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.5
> Environment: Windows 7 64 bits
> Java 1.6.0_31 x64
> maven 3.0.4
>Reporter: Laurent Malvert
> Attachments: error.log, resources-npe.tar.gz
>
>
> h2. Context and Issue
> When using the {{maven-resources-plugin}} to copy a resource to a custom
> directory using the {{copy-resources}} goal, it triggers an NPE without any
> additional information when the {{}} element is not
> specified:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
> (copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
> NullPointerException -> [Help 1]
> {noformat}
> However, the documentation at: http://maven.apache.org/pom.html#Resources
> clearly states:
> {quote}
> directory: This element's value defines where the resources are to be found.
> The default directory for a build is ${basedir}/src/main/resources.
> {quote}
> Specifying it explictly with this value works as intended.
> _(Not sure if relevant to maven-resources-plugin or the MSHARED resources
> component?)_
> h2. Test Case
> Or at leat a project to reproduce.
> See the attached project for a working test case, which uses this
> configuration:
> {code}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
> copy-resources
> validate
>
> copy-resources
>
>
>
> ${basedir}/resources
>
>
>
>
>
>
> **/somefile.xml
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
[
https://jira.codehaus.org/browse/MRESOURCES-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293614#comment-293614
]
Laurent Malvert edited comment on MRESOURCES-160 at 3/7/12 7:49 PM:
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
.bq "[...] The default directory for a build is ${basedir}/src/main/resources."
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
was (Author: laurent.malvert):
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong.
However, it shouldn't really fail with an NPE without giving any helpful
information.
> NPE when copy-resources set to use the default as
> aspecified by documentation
> ---
>
> Key: MRESOURCES-160
> URL: https://jira.codehaus.org/browse/MRESOURCES-160
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.5
> Environment: Windows 7 64 bits
> Java 1.6.0_31 x64
> maven 3.0.4
>Reporter: Laurent Malvert
> Attachments: error.log, resources-npe.tar.gz
>
>
> h2. Context and Issue
> When using the {{maven-resources-plugin}} to copy a resource to a custom
> directory using the {{copy-resources}} goal, it triggers an NPE without any
> additional information when the {{}} element is not
> specified:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
> (copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
> NullPointerException -> [Help 1]
> {noformat}
> However, the documentation at: http://maven.apache.org/pom.html#Resources
> clearly states:
> {quote}
> directory: This element's value defines where the resources are to be found.
> The default directory for a build is ${basedir}/src/main/resources.
> {quote}
> Specifying it explictly with this value works as intended.
> _(Not sure if relevant to maven-resources-plugin or the MSHARED resources
> component?)_
> h2. Test Case
> Or at leat a project to reproduce.
> See the attached project for a working test case, which uses this
> configuration:
> {code}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
> copy-resources
> validate
>
> copy-resources
>
>
>
> ${basedir}/resources
>
>
>
>
>
>
> **/somefile.xml
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
[
https://jira.codehaus.org/browse/MRESOURCES-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293615#comment-293615
]
Laurent Malvert commented on MRESOURCES-160:
Hmmm, I just realized these aren't exactly the same. I followed the goal's
documentation, which then documented the {{}} by saying to look it
up in the Maven Model documentation, and I ended up there, and somehow got
mixed up between the {{}} and {{}}.
Nonetheless, the NPE seems like a pretty harsh default behavior and should
provide additional information (missing required path).
Sorry for the confusion (would be worth testing if {{}} suffers
from the same issue.
> NPE when copy-resources set to use the default as
> aspecified by documentation
> ---
>
> Key: MRESOURCES-160
> URL: https://jira.codehaus.org/browse/MRESOURCES-160
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.5
> Environment: Windows 7 64 bits
> Java 1.6.0_31 x64
> maven 3.0.4
>Reporter: Laurent Malvert
> Attachments: error.log, resources-npe.tar.gz
>
>
> h2. Context and Issue
> When using the {{maven-resources-plugin}} to copy a resource to a custom
> directory using the {{copy-resources}} goal, it triggers an NPE without any
> additional information when the {{}} element is not
> specified:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
> (copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
> NullPointerException -> [Help 1]
> {noformat}
> However, the documentation at: http://maven.apache.org/pom.html#Resources
> clearly states:
> {quote}
> directory: This element's value defines where the resources are to be found.
> The default directory for a build is ${basedir}/src/main/resources.
> {quote}
> Specifying it explictly with this value works as intended.
> _(Not sure if relevant to maven-resources-plugin or the MSHARED resources
> component?)_
> h2. Test Case
> Or at leat a project to reproduce.
> See the attached project for a working test case, which uses this
> configuration:
> {code}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
> copy-resources
> validate
>
> copy-resources
>
>
>
> ${basedir}/resources
>
>
>
>
>
>
> **/somefile.xml
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
[
https://jira.codehaus.org/browse/MRESOURCES-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293615#comment-293615
]
Laurent Malvert edited comment on MRESOURCES-160 at 3/7/12 7:56 PM:
-- Ignore this comment: removed it, I confused myself --
was (Author: laurent.malvert):
Hmmm, I just realized these aren't exactly the same. I followed the goal's
documentation, which then documented the {{}} by saying to look it
up in the Maven Model documentation, and I ended up there, and somehow got
mixed up between the {{}} and {{}}.
Nonetheless, the NPE seems like a pretty harsh default behavior and should
provide additional information (missing required path).
Sorry for the confusion (would be worth testing if {{}} suffers
from the same issue.
> NPE when copy-resources set to use the default as
> aspecified by documentation
> ---
>
> Key: MRESOURCES-160
> URL: https://jira.codehaus.org/browse/MRESOURCES-160
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.5
> Environment: Windows 7 64 bits
> Java 1.6.0_31 x64
> maven 3.0.4
>Reporter: Laurent Malvert
> Attachments: error.log, resources-npe.tar.gz
>
>
> h2. Context and Issue
> When using the {{maven-resources-plugin}} to copy a resource to a custom
> directory using the {{copy-resources}} goal, it triggers an NPE without any
> additional information when the {{}} element is not
> specified:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
> (copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
> NullPointerException -> [Help 1]
> {noformat}
> However, the documentation at: http://maven.apache.org/pom.html#Resources
> clearly states:
> {quote}
> directory: This element's value defines where the resources are to be found.
> The default directory for a build is ${basedir}/src/main/resources.
> {quote}
> Specifying it explictly with this value works as intended.
> _(Not sure if relevant to maven-resources-plugin or the MSHARED resources
> component?)_
> h2. Test Case
> Or at leat a project to reproduce.
> See the attached project for a working test case, which uses this
> configuration:
> {code}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
> copy-resources
> validate
>
> copy-resources
>
>
>
> ${basedir}/resources
>
>
>
>
>
>
> **/somefile.xml
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
[
https://jira.codehaus.org/browse/MRESOURCES-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293614#comment-293614
]
Laurent Malvert edited comment on MRESOURCES-160 at 3/7/12 7:57 PM:
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
{quote}
[...] The default directory for a build is {{$\{basedir\}/src/main/resources}}.
{quote}
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
**Careful:** in my ticket above I mention {{outputDirectory}}. Obviously I
meant {{directory}}, as shown in the example project's configuration. Sorry for
the confusion.
was (Author: laurent.malvert):
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
{quote}
[...] The default directory for a build is {{$\{basedir\}/src/main/resources}}.
{quote}
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
> NPE when copy-resources set to use the default as
> aspecified by documentation
> ---
>
> Key: MRESOURCES-160
> URL: https://jira.codehaus.org/browse/MRESOURCES-160
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.5
> Environment: Windows 7 64 bits
> Java 1.6.0_31 x64
> maven 3.0.4
>Reporter: Laurent Malvert
> Attachments: error.log, resources-npe.tar.gz
>
>
> h2. Context and Issue
> When using the {{maven-resources-plugin}} to copy a resource to a custom
> directory using the {{copy-resources}} goal, it triggers an NPE without any
> additional information when the {{}} element is not
> specified:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
> (copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
> NullPointerException -> [Help 1]
> {noformat}
> However, the documentation at: http://maven.apache.org/pom.html#Resources
> clearly states:
> {quote}
> directory: This element's value defines where the resources are to be found.
> The default directory for a build is ${basedir}/src/main/resources.
> {quote}
> Specifying it explictly with this value works as intended.
> _(Not sure if relevant to maven-resources-plugin or the MSHARED resources
> component?)_
> h2. Test Case
> Or at leat a project to reproduce.
> See the attached project for a working test case, which uses this
> configuration:
> {code}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
> copy-resources
> validate
>
> copy-resources
>
>
>
> ${basedir}/resources
>
>
>
>
>
>
> **/somefile.xml
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
[
https://jira.codehaus.org/browse/MRESOURCES-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293614#comment-293614
]
Laurent Malvert edited comment on MRESOURCES-160 at 3/7/12 7:57 PM:
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
{quote}
[...] The default directory for a build is {{$\{basedir\}/src/main/resources}}.
{quote}
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
*Careful:* in my ticket above I mention {{outputDirectory}}. Obviously I meant
{{directory}}, as shown in the example project's configuration. Sorry for the
confusion. (Can't seem to be able to re-edit the ticket itself.)
was (Author: laurent.malvert):
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
{quote}
[...] The default directory for a build is {{$\{basedir\}/src/main/resources}}.
{quote}
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
**Careful:** in my ticket above I mention {{outputDirectory}}. Obviously I
meant {{directory}}, as shown in the example project's configuration. Sorry for
the confusion.
> NPE when copy-resources set to use the default as
> aspecified by documentation
> ---
>
> Key: MRESOURCES-160
> URL: https://jira.codehaus.org/browse/MRESOURCES-160
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.5
> Environment: Windows 7 64 bits
> Java 1.6.0_31 x64
> maven 3.0.4
>Reporter: Laurent Malvert
> Attachments: error.log, resources-npe.tar.gz
>
>
> h2. Context and Issue
> When using the {{maven-resources-plugin}} to copy a resource to a custom
> directory using the {{copy-resources}} goal, it triggers an NPE without any
> additional information when the {{}} element is not
> specified:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
> (copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
> NullPointerException -> [Help 1]
> {noformat}
> However, the documentation at: http://maven.apache.org/pom.html#Resources
> clearly states:
> {quote}
> directory: This element's value defines where the resources are to be found.
> The default directory for a build is ${basedir}/src/main/resources.
> {quote}
> Specifying it explictly with this value works as intended.
> _(Not sure if relevant to maven-resources-plugin or the MSHARED resources
> component?)_
> h2. Test Case
> Or at leat a project to reproduce.
> See the attached project for a working test case, which uses this
> configuration:
> {code}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
> copy-resources
> validate
>
> copy-resources
>
>
>
> ${basedir}/resources
>
>
>
>
>
>
> **/somefile.xml
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
[jira] (MRESOURCES-160) NPE when copy-resources set to use the default as aspecified by documentation
[
https://jira.codehaus.org/browse/MRESOURCES-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293614#comment-293614
]
Laurent Malvert edited comment on MRESOURCES-160 at 3/7/12 8:06 PM:
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
{quote}
[...] The default directory for a build is {{$\{basedir\}/src/main/resources}}.
{quote}
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
*Careful:* in my ticket above (and in its *title/summary*, whoops...) I mention
{{outputDirectory}}. Obviously I meant {{directory}}, as shown in the example
project's configuration. Sorry for the confusion. (Can't seem to be able to
re-edit the ticket itself.)
was (Author: laurent.malvert):
Might be more an enhancement than a bug as the [goal's
documentation|http://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html]
indicates that this is a required parameter.
So it appears the the documentation on the maven site is wrong (actually, mayve
it's just badly worded:
{quote}
[...] The default directory for a build is {{$\{basedir\}/src/main/resources}}.
{quote}
Maybe the intent was to say that this is where resources are usually located,
not exactly that the default value for {{directory}} is supposed to be this.
However, it shouldn't really fail with an NPE without giving any helpful
information.
*Careful:* in my ticket above I mention {{outputDirectory}}. Obviously I meant
{{directory}}, as shown in the example project's configuration. Sorry for the
confusion. (Can't seem to be able to re-edit the ticket itself.)
> NPE when copy-resources set to use the default as
> aspecified by documentation
> ---
>
> Key: MRESOURCES-160
> URL: https://jira.codehaus.org/browse/MRESOURCES-160
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: copy
>Affects Versions: 2.5
> Environment: Windows 7 64 bits
> Java 1.6.0_31 x64
> maven 3.0.4
>Reporter: Laurent Malvert
> Attachments: error.log, resources-npe.tar.gz
>
>
> h2. Context and Issue
> When using the {{maven-resources-plugin}} to copy a resource to a custom
> directory using the {{copy-resources}} goal, it triggers an NPE without any
> additional information when the {{}} element is not
> specified:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources
> (copy-resources) on project NPEResourcesBug: Execution copy-resources of goal
> org.apache.maven.plugins:maven-resources-plugin:2.5:copy-resources failed.
> NullPointerException -> [Help 1]
> {noformat}
> However, the documentation at: http://maven.apache.org/pom.html#Resources
> clearly states:
> {quote}
> directory: This element's value defines where the resources are to be found.
> The default directory for a build is ${basedir}/src/main/resources.
> {quote}
> Specifying it explictly with this value works as intended.
> _(Not sure if relevant to maven-resources-plugin or the MSHARED resources
> component?)_
> h2. Test Case
> Or at leat a project to reproduce.
> See the attached project for a working test case, which uses this
> configuration:
> {code}
>
> org.apache.maven.plugins
> maven-resources-plugin
> 2.5
>
>
> copy-resources
> validate
>
> copy-resources
>
>
>
> ${basedir}/resources
>
>
>
>
>
>
> **/somefile.xml
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://ji
[jira] (MNG-5178) Substitute environment variable M2_HOME by M3_HOME
[
https://jira.codehaus.org/browse/MNG-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293620#comment-293620
]
Oliver B. Fischer commented on MNG-5178:
This is exactly that I thought how it should be handled.
> Substitute environment variable M2_HOME by M3_HOME
> --
>
> Key: MNG-5178
> URL: https://jira.codehaus.org/browse/MNG-5178
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Command Line
>Reporter: Oliver B. Fischer
>Priority: Minor
>
> Maven 3 uses the environment variable {{M2_HOME}} to point to it's
> installation directory. This variable should be replaced by {{M3_HOME}} to
> allow users to have parallel installations of Maven 2 and Maven 3 without any
> special handling of the environment variable {{M2_HOME}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
