[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336177#comment-336177
]
Chris Graham commented on MEAR-88:
--
@Anders I completely agree! I can still remember trying to sort of the mess (ie
which to use) when m2e was in the very early days. There was little to no
documentation, and it was unstable (at that time). So I needed to come up with
a maven based solution that did not require m2e. One that I've since had to use
with some of the embedded tooling.
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 2.9
>
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
> project, it will want the {{application.xml}} file in the
> {{src\main\application\META-INF}} directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
> {code:xml}
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> {code}
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. However, by default
> it will not pick up the generated (versionized) one, it will use the existing
> one in the {{src\main\application\META-INF}} directory.
> The solution to resolve this conflict is to have maven generate the
> application.xml and use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> {code:xml}
> true
> ${project.build.directory}/application.xml
> {code}
> The first line tells maven to generate a new application.xml file, by default
> in the target directory.
> The second line tells maven to use it.
> Simple!
> -Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336163#comment-336163
]
Anders Hammar commented on MEAR-88:
---
Done in [r1544314|http://svn.apache.org/r1544314]
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 2.9
>
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
> project, it will want the {{application.xml}} file in the
> {{src\main\application\META-INF}} directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
> {code:xml}
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> {code}
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. However, by default
> it will not pick up the generated (versionized) one, it will use the existing
> one in the {{src\main\application\META-INF}} directory.
> The solution to resolve this conflict is to have maven generate the
> application.xml and use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> {code:xml}
> true
> ${project.build.directory}/application.xml
> {code}
> The first line tells maven to generate a new application.xml file, by default
> in the target directory.
> The second line tells maven to use it.
> Simple!
> -Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336156#comment-336156
]
Robert Scholte commented on MEAR-88:
[~afloom] sure, go ahead. It must be clear that this is a special case. Users
of Kepler and some previous version can skip this page.
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 2.9
>
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
> project, it will want the {{application.xml}} file in the
> {{src\main\application\META-INF}} directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
> {code:xml}
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> {code}
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. However, by default
> it will not pick up the generated (versionized) one, it will use the existing
> one in the {{src\main\application\META-INF}} directory.
> The solution to resolve this conflict is to have maven generate the
> application.xml and use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> {code:xml}
> true
> ${project.build.directory}/application.xml
> {code}
> The first line tells maven to generate a new application.xml file, by default
> in the target directory.
> The second line tells maven to use it.
> Simple!
> -Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336154#comment-336154
]
Anders Hammar commented on MEAR-88:
---
Small update in [r1544293|http://svn.apache.org/r1544293].
Maybe we should add a comment that normally m2e (and m2e-wtp) should be used,
so that new users aren't sent off the wrong direction?
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 2.9
>
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
> project, it will want the {{application.xml}} file in the
> {{src\main\application\META-INF}} directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
> {code:xml}
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> {code}
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. However, by default
> it will not pick up the generated (versionized) one, it will use the existing
> one in the {{src\main\application\META-INF}} directory.
> The solution to resolve this conflict is to have maven generate the
> application.xml and use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> {code:xml}
> true
> ${project.build.directory}/application.xml
> {code}
> The first line tells maven to generate a new application.xml file, by default
> in the target directory.
> The second line tells maven to use it.
> Simple!
> -Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MEAR-88.
--
Resolution: Fixed
Fix Version/s: 2.9
Assignee: Robert Scholte
Fixed in [r1543566|http://svn.apache.org/r1543566]
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Assignee: Robert Scholte
>Priority: Trivial
> Fix For: 2.9
>
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
> project, it will want the {{application.xml}} file in the
> {{src\main\application\META-INF}} directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
> {code:xml}
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> {code}
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. However, by default
> it will not pick up the generated (versionized) one, it will use the existing
> one in the {{src\main\application\META-INF}} directory.
> The solution to resolve this conflict is to have maven generate the
> application.xml and use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> {code:xml}
> true
> ${project.build.directory}/application.xml
> {code}
> The first line tells maven to generate a new application.xml file, by default
> in the target directory.
> The second line tells maven to use it.
> Simple!
> -Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335989#comment-335989
]
Chris Graham commented on MEAR-88:
--
I'd keep it. What Robert says in Comment #1, is _mostly_ correct. Except for
all of the other eclipse embedded tools where the m2e integration is not
available. An edge case, sure, but still a valid one.
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Priority: Trivial
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
> project, it will want the {{application.xml}} file in the
> {{src\main\application\META-INF}} directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
> {code:xml}
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> {code}
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. However, by default
> it will not pick up the generated (versionized) one, it will use the existing
> one in the {{src\main\application\META-INF}} directory.
> The solution to resolve this conflict is to have maven generate the
> application.xml and use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> {code:xml}
> true
> ${project.build.directory}/application.xml
> {code}
> The first line tells maven to generate a new application.xml file, by default
> in the target directory.
> The second line tells maven to use it.
> Simple!
> -Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335916#comment-335916
]
Anders Hammar commented on MEAR-88:
---
I suggest closing this ticket as "won't fix".
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Priority: Trivial
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
> project, it will want the {{application.xml}} file in the
> {{src\main\application\META-INF}} directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
> {code:xml}
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> {code}
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. However, by default
> it will not pick up the generated (versionized) one, it will use the existing
> one in the {{src\main\application\META-INF}} directory.
> The solution to resolve this conflict is to have maven generate the
> application.xml and use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> {code:xml}
> true
> ${project.build.directory}/application.xml
> {code}
> The first line tells maven to generate a new application.xml file, by default
> in the target directory.
> The second line tells maven to use it.
> Simple!
> -Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MEAR-88:
---
Description:
This could be implemented as another example.
Eclipse and Maven Integration
If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
project, it will want the {{application.xml}} file in the
{{src\main\application\META-INF}} directory.
If you edit application.xml using the WTP based Application Deployment
Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
name of the modules. Here is an example:
{code:xml}
http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
FireDragon
FireDragonWeb.war
firedragon
{code}
Obviously this does not have the typical maven based version naming convention
applied to it. This allows us to run the application internally within
eclipse/rsa using the test environments.
However, when maven is used to create the ear using mvn package, it will create
the versionised application.xml file, if told to. However, by default it will
not pick up the generated (versionized) one, it will use the existing one in
the {{src\main\application\META-INF}} directory.
The solution to resolve this conflict is to have maven generate the
application.xml and use the generated one as opposed to the existing one.
This can be achieved via these two directives:
{code:xml}
true
${project.build.directory}/application.xml
{code}
The first line tells maven to generate a new application.xml file, by default
in the target directory.
The second line tells maven to use it.
Simple!
-Chris
was:
This could be implemented as another example.
Eclipse and Maven Integration
If you have used mvn eclipse:eclipse to generate the metadata for an EAR
project, it will want the application.xml file in the
src\main\application\META-INF directory.
If you edit application.xml using the WTP based Application Deployment
Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
name of the modules. Here is an example:
http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
FireDragon
FireDragonWeb.war
firedragon
Obviously this does not have the typical maven based version naming convention
applied to it. This allows us to run the application internally within
eclipse/rsa using the test environments.
However, when maven is used to create the ear using mvn package, it will create
the versionised application.xml file, if told to. However, by default it will
not pick up the generated (versionized) one, it will use the existing one in
the src\main\application\META-INF directory.
The solution to resolve this conflict is to have maven generate the
application.xml and use the generated one as opposed to the existing one.
This can be achieved via these two directives:
true
${project.build.directory}/application.xml
The first line tells maven to generate a new application.xml file, by default
in the target directory.
The second line tells maven to use it.
Simple!
-Chris
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Priority: Trivial
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR
> project, it will want the {{application.xml}} file in the
> {{src\main\application\META-INF}} directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
> {code:xml}
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> {code}
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. Ho
[jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
[
https://jira.codehaus.org/browse/MEAR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335767#comment-335767
]
Robert Scholte commented on MEAR-88:
Is it still worth adding this page? I'd expect that both Eclipse and the
M2Eclipse integration are mature enough to support this without specific
adjustments.
> Improve documentation on combining Eclipse and Maven Integration
>
>
> Key: MEAR-88
> URL: https://jira.codehaus.org/browse/MEAR-88
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Reporter: Chris Graham
>Priority: Trivial
>
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used mvn eclipse:eclipse to generate the metadata for an EAR
> project, it will want the application.xml file in the
> src\main\application\META-INF directory.
> If you edit application.xml using the WTP based Application Deployment
> Descriptor editor, it will use the name of the projects (Web, EJB etc) as the
> name of the modules. Here is an example:
>
> http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4">
> FireDragon
>
>
> FireDragonWeb.war
> firedragon
>
>
>
> Obviously this does not have the typical maven based version naming
> convention applied to it. This allows us to run the application internally
> within eclipse/rsa using the test environments.
> However, when maven is used to create the ear using mvn package, it will
> create the versionised application.xml file, if told to. However, by default
> it will not pick up the generated (versionized) one, it will use the existing
> one in the src\main\application\META-INF directory.
> The solution to resolve this conflict is to have maven generate the
> application.xml and use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> true
> ${project.build.directory}/application.xml
> The first line tells maven to generate a new application.xml file, by default
> in the target directory.
> The second line tells maven to use it.
> Simple!
> -Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
