[jira] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stéphane Nicoll closed MEAR-141.
Resolution: Fixed
Time. And now it's done. I also changed the tests so that they use envEntries
to make sure ITs will pass on Maven2
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stéphane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306293#comment-306293
]
Rodion edited comment on MEAR-141 at 8/15/12 11:09 AM:
---
It was just what I mean :) - it was reverted, everybody agreed that it was
almost nothing to do with test failure and nobody have applied that patch back
for half of a year... I was thinking that may be there was something else
preventing from doing this?
was (Author: angrygami):
It was just what I mean :) - it was reverted, everybody agreed that it was
almost nothing to do with test failure and nobody have applied that patch back
for half of a year... I was thinking that may be there was something else
preventing from doing this that?
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stéphane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306293#comment-306293
]
Rodion commented on MEAR-141:
-
It was just what I mean :) - it was reverted, everybody agreed that it was
almost nothing to do with test failure and nobody have applied that patch back
for half of a year... I was thinking that may be there was something else
preventing from doing this that?
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stéphane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306291#comment-306291
]
Stéphane Nicoll commented on MEAR-141:
--
It does not work because the code was reverted. But now that I understand the
differences, we should document this and re-apply the patch indeed.
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stéphane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306290#comment-306290
]
Rodion commented on MEAR-141:
-
Somebody have plans to restore functionality provided by 1235631? Feature still
doesn't work.
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stéphane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294951#comment-294951
]
Stéphane Nicoll commented on MEAR-141:
--
ah, excellent. I understand the difference now. Thanks !
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stéphane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294948#comment-294948
]
Søren Hilmer commented on MEAR-141:
---
I checked out MEAR version 1239783 (prior to the revert)
This works for me with Maven 2.2.1 on Linux (ubuntu 11.10)
BUT you must specify the env-entry like this:
...
and NOT as in the examples
...
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stéphane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292636#comment-292636
]
Stephane Nicoll commented on MEAR-141:
--
There was some confusion at the beginning but the issue is coming from Maven 2,
not linux (probably some plexus dependency chain nightmare).
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stephane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292600#comment-292600
]
Kristian Rosenvold commented on MEAR-141:
-
>From the mailing list discussion there seemed to be some confusion as to the
>source of the problem.
I am not particularly opposed to the patch itself as long as the tests pass,
and I wanted to fix the build.
If you're using a less brain-dead client than subversion it's just two
keystrokes to revert the revert.
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stephane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292310#comment-292310
]
Stephane Nicoll edited comment on MEAR-141 at 2/21/12 2:58 AM:
---
It has nothing to do with linux. It's failing with maven 2.x
Instead of reverting, can't you reopen this issue and ignore the test instead.
It's working fine with Maven 3, we just need to figure out what is going wrong
in plexus with 2.x
was (Author: sni):
It has nothing to do with linux. It's failing with maven 2.x
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stephane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292310#comment-292310
]
Stephane Nicoll commented on MEAR-141:
--
It has nothing to do with linux. It's failing with maven 2.x
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stephane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold reopened MEAR-141:
-
I just reverted this commit in r129166 since it was breaking the IT's on 32 bit
linux.
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stephane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll closed MEAR-141.
Resolution: Fixed
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stephane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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] (MEAR-141) No way to configure generate env-entry elements in generated application.xml
[
https://jira.codehaus.org/browse/MEAR-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll updated MEAR-141:
-
Summary: No way to configure generate env-entry elements in generated
application.xml (was: No way to programmatically generate env-entry elements
in generated application.xml)
> No way to configure generate env-entry elements in generated application.xml
>
>
> Key: MEAR-141
> URL: https://jira.codehaus.org/browse/MEAR-141
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Laird Nelson
>Assignee: Stephane Nicoll
> Fix For: 2.8
>
>
> The maven-ear-plugin offers the {{security}} element for declaring
> security-role-names in a generated application.xml. It does not offer such a
> facility for generating {{env-entry}} elements. It should.
--
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
