You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by "Lars Corneliussen (Created) (JIRA)" <ji...@apache.org> on 2012/01/09 09:56:39 UTC
[jira] [Created] (NPANDAY-527) Remove the NAR packaging and
maven-webapp-plugin
Remove the NAR packaging and maven-webapp-plugin
------------------------------------------------
Key: NPANDAY-527
URL: https://issues.apache.org/jira/browse/NPANDAY-527
Project: NPanday
Issue Type: Improvement
Components: Maven Plugins
Reporter: Lars Corneliussen
Assignee: Lars Corneliussen
Fix For: 1.5.0-incubating
related discussion: http://incubator.markmail.org/thread/alcyqagktiogewmf
{quote}
maven-webapp-plugin introduces the packaging "nar" (same file extension), which creates a plain zip file containing all files from src/main/webapp (with plexus default excludes) + all referenced dlls. Doesn't seem to have any support for GAC references.
Already a year ago when I worked on it, it seemed that this plugin was out of service:
NPANDAY-256: compile-plugin does not do a install for ArtifactType.NAR
NPANDAY-256: Deprecate NAR type
1) We have no integration tests.
2) There are no unit tests.
So I'd suggest to deprecate both the type and the plugin in NPanday 1.5.0-incubating. If not, we should unify the way dependencies are 'injected'.
{quote}
{quote}
+1
I'd probably deprecate aspx and remove NAR (I doubt it is in use for the reasons you gave). Whether the precompile goal moves over depends on the answer to the above. From below, I see you have things that will supersede the copy-dependencies and package goals from that plugin.
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (NPANDAY-527) Remove the NAR packaging and
maven-webapp-plugin
Posted by "Lars Corneliussen (Work started) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on NPANDAY-527 started by Lars Corneliussen.
> Remove the NAR packaging and maven-webapp-plugin
> ------------------------------------------------
>
> Key: NPANDAY-527
> URL: https://issues.apache.org/jira/browse/NPANDAY-527
> Project: NPanday
> Issue Type: Improvement
> Components: Maven Plugins
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
> Fix For: 1.5.0-incubating
>
>
> related discussion: http://incubator.markmail.org/thread/alcyqagktiogewmf
> {quote}
> maven-webapp-plugin introduces the packaging "nar" (same file extension), which creates a plain zip file containing all files from src/main/webapp (with plexus default excludes) + all referenced dlls. Doesn't seem to have any support for GAC references.
> Already a year ago when I worked on it, it seemed that this plugin was out of service:
> NPANDAY-256: compile-plugin does not do a install for ArtifactType.NAR
> NPANDAY-256: Deprecate NAR type
> 1) We have no integration tests.
> 2) There are no unit tests.
> So I'd suggest to deprecate both the type and the plugin in NPanday 1.5.0-incubating. If not, we should unify the way dependencies are 'injected'.
> {quote}
> {quote}
> +1
> I'd probably deprecate aspx and remove NAR (I doubt it is in use for the reasons you gave). Whether the precompile goal moves over depends on the answer to the above. From below, I see you have things that will supersede the copy-dependencies and package goals from that plugin.
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-527) Remove the NAR packaging and
maven-webapp-plugin
Posted by "Lars Corneliussen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen resolved NPANDAY-527.
---------------------------------------
Resolution: Fixed
This was yet done.
> Remove the NAR packaging and maven-webapp-plugin
> ------------------------------------------------
>
> Key: NPANDAY-527
> URL: https://issues.apache.org/jira/browse/NPANDAY-527
> Project: NPanday
> Issue Type: Improvement
> Components: Maven Plugins
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
> Fix For: 1.5.0-incubating
>
>
> related discussion: http://incubator.markmail.org/thread/alcyqagktiogewmf
> {quote}
> maven-webapp-plugin introduces the packaging "nar" (same file extension), which creates a plain zip file containing all files from src/main/webapp (with plexus default excludes) + all referenced dlls. Doesn't seem to have any support for GAC references.
> Already a year ago when I worked on it, it seemed that this plugin was out of service:
> NPANDAY-256: compile-plugin does not do a install for ArtifactType.NAR
> NPANDAY-256: Deprecate NAR type
> 1) We have no integration tests.
> 2) There are no unit tests.
> So I'd suggest to deprecate both the type and the plugin in NPanday 1.5.0-incubating. If not, we should unify the way dependencies are 'injected'.
> {quote}
> {quote}
> +1
> I'd probably deprecate aspx and remove NAR (I doubt it is in use for the reasons you gave). Whether the precompile goal moves over depends on the answer to the above. From below, I see you have things that will supersede the copy-dependencies and package goals from that plugin.
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira