You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2007/04/13 21:31:15 UTC
[jira] Created: (DIRSERVER-900) Reduce the number of jars
Reduce the number of jars
-------------------------
Key: DIRSERVER-900
URL: https://issues.apache.org/jira/browse/DIRSERVER-900
Project: Directory ApacheDS
Issue Type: Improvement
Affects Versions: 1.5.0
Reporter: Emmanuel Lecharny
Fix For: 1.5.1
We have a hell too much jars. We should reduce the bumber of jars to 2 or 3 for the core serveur, plus one for each suported protocol.
shared-ldap.jar make sense, so is apacheds.jar, maybe daemon.jar plus :
- protocol-ldap.jar
- protocol-kerberos.jar,
- protocol-changepw.jar,
- protocol-dhcp
- protocol-dns
- protocol-ntp
We may also have one more jar, for the backend, like a backend-jdbm.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (DIRSERVER-900) Reduce the number of jars
Posted by Ole Ersoy <ol...@gmail.com>.
What if we define various usage scenarios and then
figure out the best way to please customers (Users, developers)?
Here's a few.
ApacheDS Development:
Put all the jars in a maven repository
and provide clean documentation indicating
what developers need to use when accessing
ApacheDS APIs.
ApacheDS Install:
The RPM Installer will have 1 installer rpm,
that pulls all other RPM dependencies, that
have a 1:1 correspondence with the maven jars.
I think the other *NIXs will have a similar approach
with an FHS file layout.
Need to figure out windows still.
I would think that it would be possible to just provide
a small RPM like installer, and then have the OSGi container
pull and install the other jars that it needs....like the Eclipse
Update service does.
Are there any other scenarios we need to consider?
Cheers,
- Ole
Alex Karasulu wrote:
> Yeah I agree that we have two apposing things to engineer around. OSGi
> pushes to more jars and most users will want one for the whole project.
> I think we can achieve both goals with a little maven magic.
>
> We just need this before we start moving in the path of breaking up jars
> into more jars. It will be nice to just have a single assembly for
> ApacheDS distributed with maven. I think the server-main was supposed
> to do this but we're not uploading the assembly to the m2 repo but the
> compiled empty artifact. We definitely need to fix this project so
> users can just us it with one jar. Perhaps we might change it's name to
> best indicate this fact?
>
> WDYT about calling it something like apacheds-all or apacheds-complete?
>
> Alex
>
> On 4/13/07, *Emmanuel Lecharny* < elecharny@gmail.com
> <ma...@gmail.com>> wrote:
>
> Alex Karasulu a écrit :
>
> > We're actually going to be going in the opposite direction with OSGi
> > when we
> > break things down into fine grained services. We may reach 100 jars
> > if we
> > do it right.
>
> I don't think that this direction is incompatible with another target,
> which is a packaged version (and this is the target I was talking about
> in this JIRA)
>
> >
> > We can use an assembly to create one jar if that makes people
> happy. But
> > this JIRA is a waste considering our direction.
>
> Make people happy seems important to me :)
> Just consider that micro-decision (like create an hundred of jars for
> internal reasons) should not be opposed to macro-decision (packaging the
> server in a couple of jars for people hapiness), but it's obviously
> another task for us (vreating the pckages, managing them, ect...).
>
> I personnaly think that delivering a server composed of an hundred of
> jars for technical reasons like OSGI, and to impose this choice to user
> to be just a wrong move. Not that OSGI is the bad direction, but users
> should not be aware of that if they don't want to be.
>
> Of course, I just express my very own opinion here, not the project
> opinion. We will have to discuss this point, for sure !
>
> Emmanuel
>
>
Re: [jira] Created: (DIRSERVER-900) Reduce the number of jars
Posted by Alex Karasulu <ak...@apache.org>.
Yeah I agree that we have two apposing things to engineer around. OSGi
pushes to more jars and most users will want one for the whole project. I
think we can achieve both goals with a little maven magic.
We just need this before we start moving in the path of breaking up jars
into more jars. It will be nice to just have a single assembly for ApacheDS
distributed with maven. I think the server-main was supposed to do this but
we're not uploading the assembly to the m2 repo but the compiled empty
artifact. We definitely need to fix this project so users can just us it
with one jar. Perhaps we might change it's name to best indicate this fact?
WDYT about calling it something like apacheds-all or apacheds-complete?
Alex
On 4/13/07, Emmanuel Lecharny <el...@gmail.com> wrote:
>
> Alex Karasulu a écrit :
>
> > We're actually going to be going in the opposite direction with OSGi
> > when we
> > break things down into fine grained services. We may reach 100 jars
> > if we
> > do it right.
>
> I don't think that this direction is incompatible with another target,
> which is a packaged version (and this is the target I was talking about
> in this JIRA)
>
> >
> > We can use an assembly to create one jar if that makes people
> happy. But
> > this JIRA is a waste considering our direction.
>
> Make people happy seems important to me :)
> Just consider that micro-decision (like create an hundred of jars for
> internal reasons) should not be opposed to macro-decision (packaging the
> server in a couple of jars for people hapiness), but it's obviously
> another task for us (vreating the pckages, managing them, ect...).
>
> I personnaly think that delivering a server composed of an hundred of
> jars for technical reasons like OSGI, and to impose this choice to user
> to be just a wrong move. Not that OSGI is the bad direction, but users
> should not be aware of that if they don't want to be.
>
> Of course, I just express my very own opinion here, not the project
> opinion. We will have to discuss this point, for sure !
>
> Emmanuel
>
>
Re: [jira] Created: (DIRSERVER-900) Reduce the number of jars
Posted by Emmanuel Lecharny <el...@gmail.com>.
Alex Karasulu a écrit :
> We're actually going to be going in the opposite direction with OSGi
> when we
> break things down into fine grained services. We may reach 100 jars
> if we
> do it right.
I don't think that this direction is incompatible with another target,
which is a packaged version (and this is the target I was talking about
in this JIRA)
>
> We can use an assembly to create one jar if that makes people happy. But
> this JIRA is a waste considering our direction.
Make people happy seems important to me :)
Just consider that micro-decision (like create an hundred of jars for
internal reasons) should not be opposed to macro-decision (packaging the
server in a couple of jars for people hapiness), but it's obviously
another task for us (vreating the pckages, managing them, ect...).
I personnaly think that delivering a server composed of an hundred of
jars for technical reasons like OSGI, and to impose this choice to user
to be just a wrong move. Not that OSGI is the bad direction, but users
should not be aware of that if they don't want to be.
Of course, I just express my very own opinion here, not the project
opinion. We will have to discuss this point, for sure !
Emmanuel
Re: [jira] Created: (DIRSERVER-900) Reduce the number of jars
Posted by Alex Karasulu <ak...@apache.org>.
We're actually going to be going in the opposite direction with OSGi when we
break things down into fine grained services. We may reach 100 jars if we
do it right.
We can use an assembly to create one jar if that makes people happy. But
this JIRA is a waste considering our direction.
Alex
On 4/13/07, Emmanuel Lecharny (JIRA) <ji...@apache.org> wrote:
>
> Reduce the number of jars
> -------------------------
>
> Key: DIRSERVER-900
> URL: https://issues.apache.org/jira/browse/DIRSERVER-900
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.0
> Reporter: Emmanuel Lecharny
> Fix For: 1.5.1
>
>
> We have a hell too much jars. We should reduce the bumber of jars to 2 or
> 3 for the core serveur, plus one for each suported protocol.
>
> shared-ldap.jar make sense, so is apacheds.jar, maybe daemon.jar plus :
> - protocol-ldap.jar
> - protocol-kerberos.jar,
> - protocol-changepw.jar,
> - protocol-dhcp
> - protocol-dns
> - protocol-ntp
>
> We may also have one more jar, for the backend, like a backend-jdbm.jar
>
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Assigned: (DIRSERVER-900) Create assemblies grouping core
jars for convenience
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu reassigned DIRSERVER-900:
---------------------------------------
Assignee: Alex Karasulu (was: Emmanuel Lecharny)
> Create assemblies grouping core jars for convenience
> ----------------------------------------------------
>
> Key: DIRSERVER-900
> URL: https://issues.apache.org/jira/browse/DIRSERVER-900
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.1, 1.5.0
> Reporter: Emmanuel Lecharny
> Assignee: Alex Karasulu
> Priority: Minor
> Fix For: 1.5.4
>
>
> We have a hell too much jars. We should reduce the bumber of jars to 2 or 3 for the core serveur, plus one for each suported protocol.
> shared-ldap.jar make sense, so is apacheds.jar, maybe daemon.jar plus :
> - protocol-ldap.jar
> - protocol-kerberos.jar,
> - protocol-changepw.jar,
> - protocol-dhcp
> - protocol-dns
> - protocol-ntp
> We may also have one more jar, for the backend, like a backend-jdbm.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-900) Create assemblies grouping core
jars for convenience
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-900:
----------------------------------------
Fix Version/s: (was: 1.5.2)
1.5.3
Postponed.
> Create assemblies grouping core jars for convenience
> ----------------------------------------------------
>
> Key: DIRSERVER-900
> URL: https://issues.apache.org/jira/browse/DIRSERVER-900
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.1, 1.5.0
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Minor
> Fix For: 1.5.3
>
>
> We have a hell too much jars. We should reduce the bumber of jars to 2 or 3 for the core serveur, plus one for each suported protocol.
> shared-ldap.jar make sense, so is apacheds.jar, maybe daemon.jar plus :
> - protocol-ldap.jar
> - protocol-kerberos.jar,
> - protocol-changepw.jar,
> - protocol-dhcp
> - protocol-dns
> - protocol-ntp
> We may also have one more jar, for the backend, like a backend-jdbm.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-900) Create assemblies grouping core
jars for convenience
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-900:
------------------------------------
Priority: Minor (was: Major)
Affects Version/s: 1.5.1
Fix Version/s: (was: 1.5.1)
1.5.2
Assignee: Emmanuel Lecharny
Summary: Create assemblies grouping core jars for convenience (was: Reduce the number of jars)
Yes this is a good idea. I just made the subject of this issue much clearer.
> Create assemblies grouping core jars for convenience
> ----------------------------------------------------
>
> Key: DIRSERVER-900
> URL: https://issues.apache.org/jira/browse/DIRSERVER-900
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.1, 1.5.0
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Minor
> Fix For: 1.5.2
>
>
> We have a hell too much jars. We should reduce the bumber of jars to 2 or 3 for the core serveur, plus one for each suported protocol.
> shared-ldap.jar make sense, so is apacheds.jar, maybe daemon.jar plus :
> - protocol-ldap.jar
> - protocol-kerberos.jar,
> - protocol-changepw.jar,
> - protocol-dhcp
> - protocol-dns
> - protocol-ntp
> We may also have one more jar, for the backend, like a backend-jdbm.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-900) Create assemblies grouping core jars
for convenience
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu closed DIRSERVER-900.
-----------------------------------
Resolution: Fixed
http://svn.apache.org/viewvc?view=rev&revision=691834
> Create assemblies grouping core jars for convenience
> ----------------------------------------------------
>
> Key: DIRSERVER-900
> URL: https://issues.apache.org/jira/browse/DIRSERVER-900
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.1, 1.5.0
> Reporter: Emmanuel Lecharny
> Assignee: Alex Karasulu
> Priority: Minor
> Fix For: 1.5.4
>
>
> We have a hell too much jars. We should reduce the bumber of jars to 2 or 3 for the core serveur, plus one for each suported protocol.
> shared-ldap.jar make sense, so is apacheds.jar, maybe daemon.jar plus :
> - protocol-ldap.jar
> - protocol-kerberos.jar,
> - protocol-changepw.jar,
> - protocol-dhcp
> - protocol-dns
> - protocol-ntp
> We may also have one more jar, for the backend, like a backend-jdbm.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-900) Create assemblies grouping core
jars for convenience
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-900:
------------------------------------
Fix Version/s: (was: 1.5.3)
1.5.4
Would like to see this done for 1.5.4 - we need an apacheds-all.jar
> Create assemblies grouping core jars for convenience
> ----------------------------------------------------
>
> Key: DIRSERVER-900
> URL: https://issues.apache.org/jira/browse/DIRSERVER-900
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.1, 1.5.0
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Minor
> Fix For: 1.5.4
>
>
> We have a hell too much jars. We should reduce the bumber of jars to 2 or 3 for the core serveur, plus one for each suported protocol.
> shared-ldap.jar make sense, so is apacheds.jar, maybe daemon.jar plus :
> - protocol-ldap.jar
> - protocol-kerberos.jar,
> - protocol-changepw.jar,
> - protocol-dhcp
> - protocol-dns
> - protocol-ntp
> We may also have one more jar, for the backend, like a backend-jdbm.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-900) Reduce the number of jars
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488795 ]
Emmanuel Lecharny commented on DIRSERVER-900:
---------------------------------------------
I have to add that I'm talking about a packaged version, for people who want to use the server as a whole.
> Reduce the number of jars
> -------------------------
>
> Key: DIRSERVER-900
> URL: https://issues.apache.org/jira/browse/DIRSERVER-900
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.0
> Reporter: Emmanuel Lecharny
> Fix For: 1.5.1
>
>
> We have a hell too much jars. We should reduce the bumber of jars to 2 or 3 for the core serveur, plus one for each suported protocol.
> shared-ldap.jar make sense, so is apacheds.jar, maybe daemon.jar plus :
> - protocol-ldap.jar
> - protocol-kerberos.jar,
> - protocol-changepw.jar,
> - protocol-dhcp
> - protocol-dns
> - protocol-ntp
> We may also have one more jar, for the backend, like a backend-jdbm.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.