nchez
Sent: Tuesday, December 12, 2006 5:48 AM
To: Maven Developers List
Subject: Re: maven2 repository of eclipse jars
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
> - the 4th token MUST be separated with "-" in maven, while in osgi
> MUST be "." (this
On 12 Dec 06, at 4:18 AM 12 Dec 06, Tom Huybrechts wrote:
On 12/12/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
This message (1) on pde-build-dev contains the state resolver as an
attachment. I used this to calculate access rules for the JDT
compiler, and to generate POMs for bundles.
http://d
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
- the 4th token MUST be separated with "-" in maven, while in osgi
MUST be "." (this is handled by the make-artifacts goal actually). A
version like 1.2.3-4 in maven is parsed as [major 1, minor 2, patch 3,
build 4], a version like 1.2.3.4
On 12/12/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 11 Dec 06, at 10:25 PM 11 Dec 06, Scott Lewis wrote:
> Hi Jason,
>
>
> What is the State resolver?
Dependency resolver. Basically a state machine that consumes OSGi
dependency information, determines what's missing and asks for more.
How
On 11 Dec 06, at 10:25 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
What is the State resolver?
Dependency resolver. Basically a state machine that consumes OSGi
dependency information, determines what's missing and asks for more.
How the conditions are satisfied is up to the implementati
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 9:10 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
So m2eclipse *does* depend upon the Maven embedder currently...and at
the moment there is no way to use the meta info in manifest.mf,
plugin.xml, (and read/changed in memory
On 11 Dec 06, at 9:10 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
So m2eclipse *does* depend upon the Maven embedder currently...and
at the moment there is no way to use the meta info in manifest.mf,
plugin.xml, (and read/changed in memory in the PDE) to 'build' a
pom
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 8:22 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements can
be specified at the level of individual
On 11 Dec 06, at 8:22 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements
can be specified at the level of individual bundles/plugins and
at the lev
Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements can
be specified at the level of individual bundles/plugins and at the
level of features (sets of plugins).
This is described in th
On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements can
be specified at the level of individual bundles/plugins and at the
level of features (sets of plugins).
This is described in that document under these subsect
Hi Tom,
Tom Huybrechts wrote:
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
> In any Eclipse install, each Import-Package is provided by at least
> one bundle, and you can make a POM dependency on that bundle. It is
> quite easy
Hi Fabrizio,
Fabrizio Giustina wrote:
On 12/11/06, Scott Lewis <[EMAIL PROTECTED]> wrote:
There is a (recently proposed/adopted) version numbering spec that
describes using the qualifier segment to distinguish between release,
integration, and nightly builds. See here for the details:
I can
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
> In any Eclipse install, each Import-Package is provided by at least
> one bundle, and you can make a POM dependency on that bundle. It is
> quite easy to implement this by feeding al
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
In any Eclipse install, each Import-Package is provided by at least
one bundle, and you can make a POM dependency on that bundle. It is
quite easy to implement this by feeding all bundles in the install
into the resolver and having it calcula
- last but not least: package-level dependencies can't be handled by
maven as is. IMHO this could not be a big problem at the moment: you
could be forced to manually add transitive dependencies but at the
end it doesn't really hurt (BTW, in eclipse builds package-level
dependencies are very rare
On 12/11/06, Scott Lewis <[EMAIL PROTECTED]> wrote:
There is a (recently proposed/adopted) version numbering spec that
describes using the qualifier segment to distinguish between release,
integration, and nightly builds. See here for the details:
I can see that the docs outline rules in choos
Hi Fabrizio,
A small clarification below
Fabrizio Giustina wrote:
Hi Graham
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
These two features together, with some scripting and a place to host the
repository, is in theory all that would be needed to make eclipse jars
automatically avai
Hi Graham
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
These two features together, with some scripting and a place to host the
repository, is in theory all that would be needed to make eclipse jars
automatically available to maven users.
I think that at the moment having a manually-
Scott Lewis is already helping with eclipse-maven relationship
This is a proposal for a new project at Eclipse foundation that will
increase this collaboration http://www.eclipse.org/proposals/kepler/
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
Please consider http://jira.codehaus.org
Please consider http://jira.codehaus.org/browse/MECLIPSE-201 if you
want to deploy these artifacts to central. Once the POMs are out
released, they can't be changed untill there is a new release.
Would'nt it be a good idea to try to involve people from Eclipse in this ?
Tom
On 12/11/06, Graham
the idea is to setup a repository with eclipse artifacts generated
from install-files and sync org.eclipse.* from there to the central
maven repo, not to create new things in ibiblio
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Carlos Sanchez wrote:
> that sounds good and can be setup
Carlos Sanchez wrote:
that sounds good and can be setup as if it were another mirror, the
important questions
who will volunteer to do it?
is enough people asking for them that it makes sense?
In theory, keeping such a repository up to date could be done from a
zone, and it's not a problem fo
that sounds good and can be setup as if it were another mirror, the
important questions
who will volunteer to do it?
is enough people asking for them that it makes sense?
On 12/11/06, Graham Leggett <[EMAIL PROTECTED]> wrote:
Hi all,
I have seen some effort scattered here and there for providin
24 matches
Mail list logo
