[jbosstools-dev] Libmanagement issues

[Max Rydahl Andersen]

> I find the solution which Dali uses for libmanagement on project 
> creation step.
> They have composite which allows to user to add libraries when he 
> create project.
JSF has it to, it is what Snjezana uses for some of the Maven 
integration we have.
afaik, she enabled that for Seam already. Something we need to see how 
we get it applied to as
much as possible elsewhere too.

Just to be precise, we should *not* be using user defined libraries 
(UDL) or come up with out own way of getting stuff online though.
UDL's are not sharable and there exist many (better) defacto ways of 
getting libraries (i.e. maven, ivy etc.)

What does make sense is that we enable users to use these defacto 
methods to decouple the library management from
the IDE and let it be used outside the IDE too. That is why the Maven 
integration is so important.

The only place we plan on having IDE specific lib management is for the 
classpath container of the server runtime -
that is where "Server provides the runtime" option comes to play. This 
is what we should and do use for non-maven projects
and what we use today.

p.s. what is RedHatDevList ? I've added jbosstools-dev too.

/max
>
>
> The libraries could be managed by eclipse's preferences, or could be 
> downloaded from the internet.
>
>
>
>
>
> This is standard feature for faceted projects.
> (see 
> org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate,
> org.eclipse.jst.common.project.facet.ui.libprov.LibraryProviderFrameworkUi) 
>
> ---
>
> If we want some *specific* libraries to be added (or we want to help 
> to user) we could do it like dtp helps with jdbc drivers when you 
> creates new ConnectionProfile.
>
>
>
> Is this we are looking for libmanagement?