[
https://issues.apache.org/jira/browse/NPANDAY-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Corneliussen updated NPANDAY-488:
--------------------------------------
Description:
MSDeploy is an extensible tool for creating deployment packages, which then can
be deployed to IIS (or Windows Services, e.g.)
This is also a prerequisite for Azure Web Roles.
h2. High-level Requirements
- Must support Package creation
- Must support full MSDeploy feature set (through -source:manifest?)
- Must choose reasonable defaults for file inclusion
- Must be configurable from the VS Add-in
- Should support XDT transformations
- Should support filtering (Maven-Properties)
- Should support Parametrization (through -declareParamFile)
- Should make it hard to let default connection strings and passwords "leak"
into the package
h2. Implementation Details
- (?) instead of reinventing the wheel, we could utilize
maven-assembly-plugin:single with package-type "dir"
-- {color:red}or:{color} Syntax should be similar to maven-assembly-plugin;
maybe code reuse is possible?
-- Externalized descriptors for file-inclusions should be possible (NPanday
then provides reasonable defaults)
- Package type is named {{msdeploy-package}} with extension {{msdeploy.zip}}
(must end with .zip)
- XDT should be delegated to MSBuild (partially depends on NPANDAY-486)
h2. Sample Plugin Configuration
{code}
// todo
{code}
was:
MSDeploy is an extensible tool for creating deployment packages, which then can
be deployed to IIS (or Windows Services, e.g.)
This is also a prerequisite for Azure Web Roles.
h2. Considerations
- a new package type {{msdeploy-package}} with extension {{msdeploy.zip}} (must
end with .zip)
- must be configurable from the VS Add-in
- we should consider running XDT config-transforms:
-- Either via MSBuild/TransformXml through
http://code.google.com/p/xdt/downloads/list
-- Connection strings and passwords should be removed by default?
- todo...
> MSDeploy Packaging for Web Applications (also Azure Web Roles)
> --------------------------------------------------------------
>
> Key: NPANDAY-488
> URL: https://issues.apache.org/jira/browse/NPANDAY-488
> Project: NPanday
> Issue Type: New Feature
> Components: Maven Plugins, Visual Studio Add-in
> Affects Versions: 1.4-incubating
> Reporter: Lars Corneliussen
> Assignee: Lars Corneliussen
>
> MSDeploy is an extensible tool for creating deployment packages, which then
> can be deployed to IIS (or Windows Services, e.g.)
> This is also a prerequisite for Azure Web Roles.
> h2. High-level Requirements
> - Must support Package creation
> - Must support full MSDeploy feature set (through -source:manifest?)
> - Must choose reasonable defaults for file inclusion
> - Must be configurable from the VS Add-in
> - Should support XDT transformations
> - Should support filtering (Maven-Properties)
> - Should support Parametrization (through -declareParamFile)
> - Should make it hard to let default connection strings and passwords "leak"
> into the package
> h2. Implementation Details
> - (?) instead of reinventing the wheel, we could utilize
> maven-assembly-plugin:single with package-type "dir"
> -- {color:red}or:{color} Syntax should be similar to maven-assembly-plugin;
> maybe code reuse is possible?
> -- Externalized descriptors for file-inclusions should be possible (NPanday
> then provides reasonable defaults)
> - Package type is named {{msdeploy-package}} with extension {{msdeploy.zip}}
> (must end with .zip)
> - XDT should be delegated to MSBuild (partially depends on NPANDAY-486)
> h2. Sample Plugin Configuration
> {code}
> // todo
> {code}
--
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
