You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eric Miles (JIRA)" <ji...@codehaus.org> on 2009/11/30 20:09:55 UTC
[jira] Created: (MEAR-117) Ear resource filtering fails if target
destination doesn't exist
Ear resource filtering fails if target destination doesn't exist
----------------------------------------------------------------
Key: MEAR-117
URL: http://jira.codehaus.org/browse/MEAR-117
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.4
Environment: Windows XP, Maven 2.0.9
Reporter: Eric Miles
In our project structure, we have src/main/application/APP-INF/classes and in this folder contains all of our resources. The desired final outcome is to have an ear with APP-INF/classes with the filtered resources. There are no other sources in this ear module so when it is time for the ear plugin to filter, we receive an error similar to the following:
Embedded error: C:\projects\hrs2-workspace\hrs2-ear\target\hrs2-ear-2.0.0-SNAPSHOT\APP-INF\app.properties (The system cannot find the path specified)
If I create the ${project.build.directory}/${project.build.finalName}/APP-INF/classes directory on disk before I package, I get no error. I would think that the resource mechanism would be responsible for creating the destination in addition to copying/filtering.
--
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: (MEAR-117) Ear resource filtering fails if target
destination doesn't exist
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll updated MEAR-117:
---------------------------------
Fix Version/s: 2.4.1
> Ear resource filtering fails if target destination doesn't exist
> ----------------------------------------------------------------
>
> Key: MEAR-117
> URL: http://jira.codehaus.org/browse/MEAR-117
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
> Reporter: Eric Miles
> Assignee: Stephane Nicoll
> Fix For: 2.4.1
>
>
> In our project structure, we have src/main/application/APP-INF/classes and in this folder contains all of our resources. The desired final outcome is to have an ear with APP-INF/classes with the filtered resources. There are no other sources in this ear module so when it is time for the ear plugin to filter, we receive an error similar to the following:
> Embedded error: C:\projects\hrs2-workspace\hrs2-ear\target\hrs2-ear-2.0.0-SNAPSHOT\APP-INF\app.properties (The system cannot find the path specified)
> If I create the ${project.build.directory}/${project.build.finalName}/APP-INF/classes directory on disk before I package, I get no error. I would think that the resource mechanism would be responsible for creating the destination in addition to copying/filtering.
--
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: (MEAR-117) Ear resource filtering fails if target
destination doesn't exist
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll closed MEAR-117.
--------------------------------
Resolution: Fixed
Done. Snapshot deployed.
> Ear resource filtering fails if target destination doesn't exist
> ----------------------------------------------------------------
>
> Key: MEAR-117
> URL: http://jira.codehaus.org/browse/MEAR-117
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
> Reporter: Eric Miles
> Assignee: Stephane Nicoll
> Fix For: 2.4.1
>
>
> In our project structure, we have src/main/application/APP-INF/classes and in this folder contains all of our resources. The desired final outcome is to have an ear with APP-INF/classes with the filtered resources. There are no other sources in this ear module so when it is time for the ear plugin to filter, we receive an error similar to the following:
> Embedded error: C:\projects\hrs2-workspace\hrs2-ear\target\hrs2-ear-2.0.0-SNAPSHOT\APP-INF\app.properties (The system cannot find the path specified)
> If I create the ${project.build.directory}/${project.build.finalName}/APP-INF/classes directory on disk before I package, I get no error. I would think that the resource mechanism would be responsible for creating the destination in addition to copying/filtering.
--
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: (MEAR-117) Ear resource filtering
fails if target destination doesn't exist
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206081#action_206081 ]
Stephane Nicoll edited comment on MEAR-117 at 1/10/10 8:19 AM:
---------------------------------------------------------------
please attach a project that reproduces the issue
was (Author: sni):
please attach a projet that reproduces the issue
> Ear resource filtering fails if target destination doesn't exist
> ----------------------------------------------------------------
>
> Key: MEAR-117
> URL: http://jira.codehaus.org/browse/MEAR-117
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
> Reporter: Eric Miles
>
> In our project structure, we have src/main/application/APP-INF/classes and in this folder contains all of our resources. The desired final outcome is to have an ear with APP-INF/classes with the filtered resources. There are no other sources in this ear module so when it is time for the ear plugin to filter, we receive an error similar to the following:
> Embedded error: C:\projects\hrs2-workspace\hrs2-ear\target\hrs2-ear-2.0.0-SNAPSHOT\APP-INF\app.properties (The system cannot find the path specified)
> If I create the ${project.build.directory}/${project.build.finalName}/APP-INF/classes directory on disk before I package, I get no error. I would think that the resource mechanism would be responsible for creating the destination in addition to copying/filtering.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MEAR-117) Ear resource filtering fails if
target destination doesn't exist
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MEAR-117 started by Stephane Nicoll.
> Ear resource filtering fails if target destination doesn't exist
> ----------------------------------------------------------------
>
> Key: MEAR-117
> URL: http://jira.codehaus.org/browse/MEAR-117
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
> Reporter: Eric Miles
> Assignee: Stephane Nicoll
> Fix For: 2.4.1
>
>
> In our project structure, we have src/main/application/APP-INF/classes and in this folder contains all of our resources. The desired final outcome is to have an ear with APP-INF/classes with the filtered resources. There are no other sources in this ear module so when it is time for the ear plugin to filter, we receive an error similar to the following:
> Embedded error: C:\projects\hrs2-workspace\hrs2-ear\target\hrs2-ear-2.0.0-SNAPSHOT\APP-INF\app.properties (The system cannot find the path specified)
> If I create the ${project.build.directory}/${project.build.finalName}/APP-INF/classes directory on disk before I package, I get no error. I would think that the resource mechanism would be responsible for creating the destination in addition to copying/filtering.
--
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: (MEAR-117) Ear resource filtering fails if target
destination doesn't exist
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206081#action_206081 ]
Stephane Nicoll commented on MEAR-117:
--------------------------------------
please attach a projet that reproduces the issue
> Ear resource filtering fails if target destination doesn't exist
> ----------------------------------------------------------------
>
> Key: MEAR-117
> URL: http://jira.codehaus.org/browse/MEAR-117
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
> Reporter: Eric Miles
>
> In our project structure, we have src/main/application/APP-INF/classes and in this folder contains all of our resources. The desired final outcome is to have an ear with APP-INF/classes with the filtered resources. There are no other sources in this ear module so when it is time for the ear plugin to filter, we receive an error similar to the following:
> Embedded error: C:\projects\hrs2-workspace\hrs2-ear\target\hrs2-ear-2.0.0-SNAPSHOT\APP-INF\app.properties (The system cannot find the path specified)
> If I create the ${project.build.directory}/${project.build.finalName}/APP-INF/classes directory on disk before I package, I get no error. I would think that the resource mechanism would be responsible for creating the destination in addition to copying/filtering.
--
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: (MEAR-117) Ear resource filtering fails if target
destination doesn't exist
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207163#action_207163 ]
Stephane Nicoll commented on MEAR-117:
--------------------------------------
raaah gotcha, regression because now we use the maven-filtering thingy
> Ear resource filtering fails if target destination doesn't exist
> ----------------------------------------------------------------
>
> Key: MEAR-117
> URL: http://jira.codehaus.org/browse/MEAR-117
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.9
> Reporter: Eric Miles
> Assignee: Stephane Nicoll
> Fix For: 2.4.1
>
>
> In our project structure, we have src/main/application/APP-INF/classes and in this folder contains all of our resources. The desired final outcome is to have an ear with APP-INF/classes with the filtered resources. There are no other sources in this ear module so when it is time for the ear plugin to filter, we receive an error similar to the following:
> Embedded error: C:\projects\hrs2-workspace\hrs2-ear\target\hrs2-ear-2.0.0-SNAPSHOT\APP-INF\app.properties (The system cannot find the path specified)
> If I create the ${project.build.directory}/${project.build.finalName}/APP-INF/classes directory on disk before I package, I get no error. I would think that the resource mechanism would be responsible for creating the destination in addition to copying/filtering.
--
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