Hi Felix,
I followed the indications given by David and added the correct files to
src/main/appended-resources/META-INF to the projects that needed to include
others licenses and notice informations.
Everything is fine now:
- The MANIFEST.MF files are now automatically generated by Maven
Pierre-Arnaud Marcelot schrieb:
Hi Felix,
I followed the indications given by David and added the correct files
to src/main/appended-resources/META-INF to the projects that needed to
include others licenses and notice informations.
Everything is fine now:
* The MANIFEST.MF files are
Hi Felix,
Actually, I've got an issue with this solution... :(
When you erase entirely your Maven local repository, there's an issue
because the UpdateSite project refers to the help projects, which have not
been built yet...
So the build fails.
I noticed that when I was switching the version
Pierre-Arnaud Marcelot schrieb:
Hi Felix,
Actually, I've got an issue with this solution... :(
When you erase entirely your Maven local repository, there's an issue
because the UpdateSite project refers to the help projects, which have
not been built yet...
So the build fails.
I noticed
On Fri, Sep 26, 2008 at 1:58 PM, Felix Knecht [EMAIL PROTECTED] wrote:
You're absolutely right, I should have thought about this. Profile
modules are built after the non profile modules. So we had in fact a
back log of 1 build in the help plugins :-(
I'll fix this.
I tried to fix it but it
Pierre-Arnaud Marcelot schrieb:
On Fri, Sep 26, 2008 at 1:58 PM, Felix Knecht [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
You're absolutely right, I should have thought about this. Profile
modules are built after the non profile modules. So we had in fact a
back log of 1
On Fri, Sep 26, 2008 at 3:08 PM, Felix Knecht [EMAIL PROTECTED] wrote:
I think I've found a solution doing both, but I need to retest again.
The ugly thing is that have the help-pom.xml goes into each
*help/pom.xml ...
Ok cool... If it saves us a lot of time, it's not so ugly...
Thanks,
I think I've found a solution doing both, but I need to retest again.
The ugly thing is that have the help-pom.xml goes into each
*help/pom.xml ...
Retests failed.
in fact you should be able to have something like
profile
idbuild-help/id
activation
file
On Fri, Sep 26, 2008 at 3:11 PM, Felix Knecht [EMAIL PROTECTED] wrote:
Retests failed.
in fact you should be able to have something like
profile
idbuild-help/id
activation
file
missing${basedir}/timestamp/missing
/file
/activation
in the
Modified: directory/studio/trunk/help-pom.xml
URL:
http://svn.apache.org/viewvc/directory/studio/trunk/help-pom.xml?rev=699310r1=699309r2=699310view=diff
==
--- directory/studio/trunk/help-pom.xml (original)
+++
Oh damn...
I thought I had set it as is:
missingtimestamp/missing
instead of
missingschemaeditor-help/timestamp/missing
Sorry about that...
What we could use a property instead of the timestamp file.
profiles
profile
activation
property
namerebuildHelp/name
Pierre-Arnaud Marcelot schrieb:
On Fri, Sep 26, 2008 at 3:11 PM, Felix Knecht [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Retests failed.
in fact you should be able to have something like
profile
idbuild-help/id
activation
file
Pierre-Arnaud Marcelot schrieb:
Oh damn...
I thought I had set it as is:
missingtimestamp/missing
instead of
missingschemaeditor-help/timestamp/missing
Sorry about that...
NP
What we could use a property instead of the timestamp file.
profiles
profile
activation
On Fri, Sep 26, 2008 at 3:46 PM, Felix Knecht [EMAIL PROTECTED] wrote:
What's the benfit of a property? Where do you set the property? You'd
need to set it on every run - We could also use a profile directly
instead of a property ...
Yeah, you're right... Using a profile directly is better.
The Core API does not handle referrals
--
Key: DIRSERVER-1272
URL: https://issues.apache.org/jira/browse/DIRSERVER-1272
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.4
[
https://issues.apache.org/jira/browse/DIRSERVER-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12634919#action_12634919
]
Emmanuel Lecharny commented on DIRSERVER-1272:
--
As a matter of fact,
Hi guys,
as i'm struggling with referrals for days now, I just discovered that
there are many places in the server which are not handling them
correctly. Atm, the only part which is sane is the protocol layer. For
embedded servers, not passing through the protocol layer, I have to say
that
Emmanuel,
On Fri, Sep 26, 2008 at 2:01 PM, Emmanuel Lecharny [EMAIL PROTECTED]wrote:
Hi guys,
as i'm struggling with referrals for days now, I just discovered that there
are many places in the server which are not handling them correctly.
I had removed referral handling from everywhere and
hi guys,
I have been working on finding ways to integrate quartz into the
server and mainly on the feature to store the
quartz scheduling data a.k.a Quartz LDAP store.
Currently quartz has two kinds of stores, In-memory and RDBMS.
Quartz uses 12 tables!! to store data in
RDBMS
Hi Alex,
I will add comments inline.
Alex Karasulu wrote:
Emmanuel,
On Fri, Sep 26, 2008 at 2:01 PM, Emmanuel Lecharny [EMAIL PROTECTED]wrote:
Hi guys,
as i'm struggling with referrals for days now, I just discovered that there
are many places in the server which are not handling them
On Fri, Sep 26, 2008 at 8:36 PM, Emmanuel Lecharny [EMAIL PROTECTED]wrote:
Alex Karasulu wrote:
Emmanuel,
On Fri, Sep 26, 2008 at 2:01 PM, Emmanuel Lecharny [EMAIL PROTECTED]
wrote:
Now, the problem is that for referrals, as we have also removed the
ReferralInterceptor from the core
21 matches
Mail list logo
