[jira] Commented: (AXIS2-4295) saaj testResource has empy targetPath
[ https://issues.apache.org/jira/browse/AXIS2-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12694541#action_12694541 ] Andreas Veithen commented on AXIS2-4295: What is the Maven version you are using? saaj testResource has empy targetPath - Key: AXIS2-4295 URL: https://issues.apache.org/jira/browse/AXIS2-4295 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: saaj Affects Versions: nightly Reporter: Jason Fager In saaj's pom.xml, the targetPath that the *.properties are being copied to is empty. This results in the build attempting to copy the file into '/' testResource targetPath/targetPath !-- Not good. -- directorytest-resources/directory includes include**/*.properties/include /includes /testResource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4295) saaj testResource has empy targetPath
[ https://issues.apache.org/jira/browse/AXIS2-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12694558#action_12694558 ] Jason Fager commented on AXIS2-4295: 2.0.8/2.1.0, maven-resource-plugin 2.3. Here's the ticket where they added absolute paths: http://jira.codehaus.org/browse/MSHARED-66 saaj testResource has empy targetPath - Key: AXIS2-4295 URL: https://issues.apache.org/jira/browse/AXIS2-4295 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: saaj Affects Versions: nightly Reporter: Jason Fager In saaj's pom.xml, the targetPath that the *.properties are being copied to is empty. This results in the build attempting to copy the file into '/' testResource targetPath/targetPath !-- Not good. -- directorytest-resources/directory includes include**/*.properties/include /includes /testResource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4295) saaj testResource has empy targetPath
[ https://issues.apache.org/jira/browse/AXIS2-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12694584#action_12694584 ] Andreas Veithen commented on AXIS2-4295: I tested with 2.0.9 and it works. The reason is explained in [1]: Starting in Maven 2.0.9, default versions of core plugins have been provided in the Super POM. This was done to provide some stability for users that are not specifying versions in their POMs. It also indicates that the default version of the maven-resources-plugin in Maven 2.0.9 is 2.2. That explains why you see this issue, while others don't. To fix this we will have a add a pluginManagement to the parent POM. [1] http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom.html saaj testResource has empy targetPath - Key: AXIS2-4295 URL: https://issues.apache.org/jira/browse/AXIS2-4295 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: saaj Affects Versions: nightly Reporter: Jason Fager In saaj's pom.xml, the targetPath that the *.properties are being copied to is empty. This results in the build attempting to copy the file into '/' testResource targetPath/targetPath !-- Not good. -- directorytest-resources/directory includes include**/*.properties/include /includes /testResource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4295) saaj testResource has empy targetPath
[ https://issues.apache.org/jira/browse/AXIS2-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12694592#action_12694592 ] Jason Fager commented on AXIS2-4295: Just for discussion's sake, why not set the targetPath to '.'? Pegging the build to a particular version of a Maven plugin, maybe that is the right way to get a repeatable build. I've never done it, though, and I kind of get a headache thinking about managing that... if you're doing it for one plugin, shouldn't you be doing it for all? But even if it is the 'right' thing, planning ahead a bit, when the time comes to bump up to the next Maven version, this change would need to be made anyways. If it works with the earlier plugin as expected, then may as well do it now, right? saaj testResource has empy targetPath - Key: AXIS2-4295 URL: https://issues.apache.org/jira/browse/AXIS2-4295 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: saaj Affects Versions: nightly Reporter: Jason Fager In saaj's pom.xml, the targetPath that the *.properties are being copied to is empty. This results in the build attempting to copy the file into '/' testResource targetPath/targetPath !-- Not good. -- directorytest-resources/directory includes include**/*.properties/include /includes /testResource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4295) saaj testResource has empy targetPath
[ https://issues.apache.org/jira/browse/AXIS2-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12694713#action_12694713 ] Andreas Veithen commented on AXIS2-4295: Anyway it is a best practice to always specify the version of all plugins. The default versions can be specified quite easily using a pluginManagement section in the parent POM. Since we know that Axis2 builds fine with Maven 2.0.9, I copied the pluginManagement section from the super POM of that Maven version to the Axis2 parent POM. That should stabilize the build with other Maven versions. Of course we should also clean up the test resources in axis2-saaj, but if I remember well, there are other strange things related to this and the targetPath is not the only problem. saaj testResource has empy targetPath - Key: AXIS2-4295 URL: https://issues.apache.org/jira/browse/AXIS2-4295 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: saaj Affects Versions: nightly Reporter: Jason Fager In saaj's pom.xml, the targetPath that the *.properties are being copied to is empty. This results in the build attempting to copy the file into '/' testResource targetPath/targetPath !-- Not good. -- directorytest-resources/directory includes include**/*.properties/include /includes /testResource -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
