[
https://issues.apache.org/jira/browse/DIRSERVER-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634407#action_12634407
]
Emmanuel Lecharny commented on DIRSERVER-1255:
----------------------------------------------
Not that I like maven either, but you have options here. The biggest problem is
that Maven will grab almost the whole internet (even more of it than the Google
indexed pages ;) when you domm your repository. It's time consuming, for sure.
For instance, you can install a maven proxy (http://archiva.apache.org/) to be
sure that it uses the 100Mbs local network instead of a slow ISDN connection.
And I'm pretty sure that's a good idea to get a stable version of the jars you
are using
<maven rant>I personnaly find it fairly dangerous to grab jars from the
internet when building a product, as you have _no_ guarantee that those jars
have not changed since the last build. This is were Maven did not get it : it's
a build system, it does not manage your configuration... Studio was built using
Ant a while back, and we stored into SVN _all_ the used jars, and we were able
to guarantee that we can get a tagged version with all the jars used to build
this specific version. This can't be done with maven, as the jars are managed
by another entity (and as there are many diffferent repos...)</mavenRant>
> unit tests fail on windows (jdbm-store and core-integ)
> ------------------------------------------------------
>
> Key: DIRSERVER-1255
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1255
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core, tools
> Affects Versions: 1.5.4
> Environment: C:\src\ad-1.5.4>mvn -version
> Maven version: 2.0.8
> Java version: 1.5.0_11
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> C:\src\ad-1.5.4>java -version
> java version "1.5.0_11"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> and running mvn from a dos command prompt
> Reporter: Norval Hope
> Priority: Blocker
> Fix For: 1.5.5
>
> Attachments: jdbm-store-test-failures.patch, test-failures.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> A checkout of
> http://svn.apache.org/repos/asf/directory/apacheds/trunk-with-dependencies
> followed by a "mvn install" fails. Initially jdbm-store/ fails with:
> Tests in error:
>
> testNoEqualityMatching(org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmIndexTest)
>
> testSingleValuedAttribute(org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmIndexTest)
> If JdbmIndexTest is moved out of the way then there are bulk failures in
> core-integ/ .
> The evidence seems to indicate that all the failures are related to deletion
> of temp directories failing due windows filesystem semantics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
