Author: brett
Date: Wed Aug 6 10:01:13 2014
New Revision: 1616144
URL: http://svn.apache.org/r1616144
Log:
formatting and typos
Modified:
incubator/npanday/trunk/site/src/site/apt/developers/design/com-references.apt
incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt
incubator/npanday/trunk/site/src/site/apt/faqs.apt
incubator/npanday/trunk/site/src/site/apt/guide/advanced/generate-project.apt
Modified:
incubator/npanday/trunk/site/src/site/apt/developers/design/com-references.apt
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/site/src/site/apt/developers/design/com-references.apt?rev=1616144&r1=1616143&r2=1616144&view=diff
==============================================================================
---
incubator/npanday/trunk/site/src/site/apt/developers/design/com-references.apt
(original)
+++
incubator/npanday/trunk/site/src/site/apt/developers/design/com-references.apt
Wed Aug 6 10:01:13 2014
@@ -20,13 +20,13 @@
COM References
- When Visual Studio compiles code that uses a COM object, it creates a
wrapper DLL. For example, compiling code in
- <<<MyProject>>> that uses <<<Shell32.dll>>> will result in both
<<<MyProject.dll>>> and <<<Interop.Shell32.dll>>>
- being created.
-
- This also needs to happen if there is a transitive dependency - if
<<<OtherProject>>> depends on <<<MyProject>>>, and
- <<<MyProject>>> uses <<<Shell32.dll>>>, then <<<Interop.Shell32.dll>>>
also needs to be available when building
- <<<OtherProject>>>.
+ When Visual Studio compiles code that uses a COM object, it creates a
wrapper DLL. For example, compiling code in
+ <<<MyProject>>> that uses <<<Shell32.dll>>> will result in both
<<<MyProject.dll>>> and <<<Interop.Shell32.dll>>>
+ being created.
+
+ This also needs to happen if there is a transitive dependency - if
<<<OtherProject>>> depends on <<<MyProject>>>, and
+ <<<MyProject>>> uses <<<Shell32.dll>>>, then <<<Interop.Shell32.dll>>> also
needs to be available when building
+ <<<OtherProject>>>.
* Requirements
@@ -62,4 +62,4 @@ COM References
* {{http://msdn.microsoft.com/en-us/magazine/cc301750.aspx}}
- []
\ No newline at end of file
+ []
Modified: incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt?rev=1616144&r1=1616143&r2=1616144&view=diff
==============================================================================
--- incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt
(original)
+++ incubator/npanday/trunk/site/src/site/apt/developers/releasing.apt Wed Aug
6 10:01:13 2014
@@ -22,7 +22,7 @@ Pre-release checklist
* Check the build is successful for both NPanday and NPanday-ITs
- * Ensure all issues in the jira for that version have been resolved, or are
moved to a later version
+ * Ensure all issues in the JIRA for that version have been resolved, or are
moved to a later version
* NPanday staging repo
{{http://vmbuild.apache.org/archiva/repository/staged-npanday/}} should be
re-created before the release to ensure that the repo only contains the
artifacts for the said release version.
@@ -32,13 +32,12 @@ Pre-release checklist
To do this, run the following command:
-----
++----+
mvn clean install -Ppre-release
-----
++----+
- Ensure that the build is successful before proceeding to the release proper.
-
-<Note: (This is needed for the signature of the artifacts to be deployed)>
+ Ensure that the build is successful before proceeding to the release proper.
+ <Note: (This is needed for the signature of the artifacts to be deployed)>
* The release manager should generate a sign key and register the key at
http://pgp.mit.edu/
@@ -70,9 +69,9 @@ Creating a Release Candidate
[[2]] Run the following command:
-----
++----+
mvn release:prepare
-----
++----+
[[3]] Fill in the following values:
Modified: incubator/npanday/trunk/site/src/site/apt/faqs.apt
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/site/src/site/apt/faqs.apt?rev=1616144&r1=1616143&r2=1616144&view=diff
==============================================================================
--- incubator/npanday/trunk/site/src/site/apt/faqs.apt (original)
+++ incubator/npanday/trunk/site/src/site/apt/faqs.apt Wed Aug 6 10:01:13 2014
@@ -50,7 +50,7 @@ NPanday Frequently Asked Questions
* Can NPanday build projects outside of Visual Studio?
- Yes. Since the NPanday Visual Studio Addin creates a POM file from your
corresponding .NET Project you can build your
+ Yes. Since the NPanday Visual Studio Add-in creates a POM file from your
corresponding .NET Project you can build your
.NET Projects using standard Apache Maven commands.
* Why use NPanday when you can build .NET Applications in Visual Studio or
MSBuild?
@@ -62,7 +62,7 @@ NPanday Frequently Asked Questions
In addition, NPanday brings Maven's dependency management and other plugins
(such as developer site generation) to
.NET projects with little additional work needed.
-* How can a custom <<<settings.xml>>> be used for the Visual Studio Addin?
+* How can a custom <<<settings.xml>>> be used for the Visual Studio Add-in?
Add the <<<\-DsettingsFile\=\[path_to_custom_settings.xml_file\]>>>
parameter when executing
<<<mvn org.apache.npanday.plugins:maven\-vsinstaller\-plugin:install>>>. For
example,
Modified:
incubator/npanday/trunk/site/src/site/apt/guide/advanced/generate-project.apt
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/site/src/site/apt/guide/advanced/generate-project.apt?rev=1616144&r1=1616143&r2=1616144&view=diff
==============================================================================
---
incubator/npanday/trunk/site/src/site/apt/guide/advanced/generate-project.apt
(original)
+++
incubator/npanday/trunk/site/src/site/apt/guide/advanced/generate-project.apt
Wed Aug 6 10:01:13 2014
@@ -83,10 +83,10 @@ mvn archetype:generate -DarchetypeArtifa
Other types of template projects are available. To use them instead, change
the <<<archetypeArtifactId>>> option to
one of the following:
- * <<<maven-artchetype-dotnet-simple>>> - simple C# project with unit tests
in the Maven directory layout
+ * <<<maven-archetype-dotnet-simple>>> - simple C# project with unit tests
in the Maven directory layout
- * <<<maven-artchetype-vb-simple>>> - simple Visual Basic project with unit
tests in the Maven directory layout
+ * <<<maven-archetype-vb-simple>>> - simple Visual Basic project with unit
tests in the Maven directory layout
- * <<<maven-artchetype-netexecutable>>> - simple project for creating a
console executable
+ * <<<maven-archetype-netexecutable>>> - simple project for creating a
console executable
[]
