mvn clean
before compiling the project with
mvn install
it may - or not - work
Emmanuel
btw, thanks, maven ! ;(
On 9/29/06,
Bastiaan Bakker (JIRA) <[EMAIL PROTECTED]> wrote:
[ http://issues.apache.org/jira/browse/DIRSERVER-749?page=comments#action_12438736 ]
Bastiaan Bakker commented on DIRSERVER-749:
-------------------------------------------
grrmbl. 1.0 branch doesn't build for me anymore due to same problem:
/home/bastiaan/sources/svn.apache.org/1.0/directory/apacheds/server-jndi/src/main/java/org/apache/directory/server/jndi/ServerContextFactory.java:[60,30] cannot find symbol
symbol : class ExecutorThreadModel
location: package org.apache.mina.common
/home/bastiaan/sources/svn.apache.org/1.0/directory/apacheds/server-jndi/src/main/java/org/apache/directory/server/jndi/ServerContextFactory.java:[74,54] package edu.emory.mathcs.backport.java.util.concurrent does not exist
so I guess that should be fixed first.
> fix issues with apacheds RPM to get it working out of the box
> -------------------------------------------------------------
>
> Key: DIRSERVER-749
> URL: http://issues.apache.org/jira/browse/DIRSERVER-749
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: installer-plugin
> Affects Versions: 1.0-RC4
> Environment: linux
> Reporter: Bastiaan Bakker
> Assigned To: Alex Karasulu
> Fix For: 1.1.0, 1.0
>
> Attachments: apacheds-branch-1.0-server-installers-rpmfix.patch, apacheds-daemon-trunk-rpmfix.patch
>
>
> The apacheds RPM has several issues that prevent it from running out of the box:
> * the init script fails to run because APACHEDS_USER is set to $USER, which is not defined at boot time
> * the init script fails to run bevause JAVA_HOME is not defined
> * the init script it is not registered to the init subsystem with chkconfig or similar
> * the config files are not marked as such, causing them to be silently overwritten when one upgrades the RPM
> * the RPM filename is not conform conventions: ${name}-${version}-${release}.${arch}.rpm
> * the location of the files (/usr/local/apacheds- 1.0_RC4) is version dependent, making upgrades cumbsome. The admin has to relocate the partitions and config files on every updgrade.
> * the sources and docs are included in the rpm, even though they are not necessary for operation.
> The RPM build mechanism for apacheds also has some issues:
> * runs rpmbuild as root, which is frowned upon by RPM gurus for security and safety reasons.
> * the generated src.rpm is not self contained, ie. one cannot do a 'rpmbuild --rebuild' with it.
> * the sudo mechanism is totally unnecessary
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Cordialement,
Emmanuel Lécharny
