IMHO, everything should be refactored in to one solution. Just go ahead.
I don't think this is intentional.
_
Lars
Am 02.05.11 11:57, schrieb Deng Ching:
Hi,
Currently, the sources and the tests are in different solutions. This makes
it harder to do refactoring -- if there are changes in the
Hi alltogether,
Just wan't to discuss some of the documented and undocumented conventions:
In the documentation file there already is a comment to keep in mind,
when reading:
~~ TODO: set a title for identifiers, since there are other
conventions. Adjust to simplify - one group for
When a non-NPanday project (in an independent Maven execution) depends on a
dotnet-executable, and tries to resolve transitive dependencies for that
project, such as dotnet-library, the build breaks for the non-NPanday
project because it fails to resolve the transitive dotnet-library
dependency.
Any project that want's to resolve references (transitive or not) need
the compile-plugin as extension in order to map from packaging to file
extension... dotnet-library - dll, dotnet-executable - exe
Workarround: Instead of specifying the packaging, you can also specify
the file extension as
Lars,
Thanks for the information. So, just to clarify, this is a generic Maven
requirement and is not NPanday-specific?
I'm working on NPANDAY-412 already, was planning to send an update later
today based on further analysis.
tc,
-john.
On Mon, May 2, 2011 at 2:01 PM, Lars Corneliussen
On 02/05/2011, at 8:02 PM, lcornelius...@apache.org wrote:
Author: lcorneliussen
Date: Mon May 2 10:02:50 2011
New Revision: 1098526
URL: http://svn.apache.org/viewvc?rev=1098526view=rev
Log:
[NPANDAY-377] Fix ITs for 377 and added a new test, that ensures, that full
file paths also
