Eclipse Community Forums: Gemini » Gemini Blueprint 1.0.0.M1 ships

Help

Home

Home » Eclipse Projects » Gemini » Gemini Blueprint 1.0.0.M1 ships(First Blueprint milestone is out!)

Show: Today's Messages :: Show Polls :: Message Navigator

Gemini Blueprint 1.0.0.M1 ships [message #543936]

Thu, 01 July 2010 07:23

Costin Leau

Messages: 45
Registered: February 2010

Member

The first milestone (1.0.0.M1) of Gemini Blueprint is available for download.

See the documentation on how to migrate/use it.

Cheers,
Costin Leau
Lead, Eclipse Gemini Blueprint

Report message to a moderator

Re: Gemini Blueprint 1.0.0.M1 ships [message #545650 is a reply to message #543936]

Thu, 08 July 2010 13:30

Werner Keil

Messages: 1087
Registered: July 2009

Senior Member

Will Gemini instantly leave the Incubator?

I noticed, both Gemini and Virgo start with 1.x or above releases.
This is rather unusual for Eclipse projects. Have you checked that is OK or
are the projects supposed to leave the incubator and have a 1.x release by
the means of Eclipse Foundation?

Cheers,
Werner

Report message to a moderator

Re: Gemini Blueprint 1.0.0.M1 ships [message #545651 is a reply to message #545650]

Thu, 08 July 2010 14:02

Costin Leau

Messages: 45
Registered: February 2010

Member

No, it won't.

As for the versioning, the current version is a milestone. 1.0 is meant to be the release that moves Gemini outside the incubator but until we get there we are pushing out milestones.
I'm not aware of any rules that forbid us to do that.

Report message to a moderator

Re: Gemini Blueprint 1.0.0.M1 ships [message #549739 is a reply to message #543936]

Tue, 27 July 2010 18:36

Werner Keil

Messages: 1087
Registered: July 2009

Senior Member

This is a multi-part message in MIME format.

------=_NextPart_000_01E5_01CB2DC2.F1BE3170
Content-Type: text/plain;
format=flowed;
charset="UTF-8";
reply-type=response
Content-Transfer-Encoding: 7bit

Hi,

What's the reason a POM from the Blueprint (hopefully outdated ;-) promotes
one form of Maven artifactId, while Gemini itself uses another?!

I lead an Eclipse project (UOMo) where the only non-Eclipse dependency is
also shaped by a group of experts around unitsofmeasure.org.

The discussion about the final artifact name lead us to your Blueprints
which as of M2 still use a "dash" style naming of artifactId:
<groupId>org.eclipse.gemini.blueprint</groupId>
<artifactId>gemini-blueprint-io</artifactId>

Gemini itself uses the OSGi bundle style like this:
<groupId>org.eclipse.gemini.naming</groupId>
<artifactId>org.eclipse.gemini.naming.impl.bundle-Incubation </artifactId>

Any reasons why this is inconsistent?

Hopefully Tycho may also shed some light on this and what it promotes as
best practice for artifactId naming, especially for OSGi-enabled
JAR-bundles?

Thanks,
Werner

------=_NextPart_000_01E5_01CB2DC2.F1BE3170
Content-Type: text/xml;
name="pom.xml"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="pom.xml"

<?xml version=3D"1.0"?>=0A=
<project>=0A=
<parent>=0A=
<artifactId>gemini-blueprint</artifactId>=0A=
<groupId>org.eclipse.gemini.blueprint</groupId>=0A=
<version>1.0.0.M2-SNAPSHOT</version>=0A=
</parent>=0A=
<modelVersion>4.0.0</modelVersion>=0A=
<groupId>org.eclipse.gemini.blueprint</groupId>=0A=
<artifactId>gemini-blueprint-io</artifactId>=0A=
<packaging>jar</packaging>=0A=
<name>Gemini Blueprint IO</name>=0A=
<url>http://www.eclipse.org/gemini/blueprint/</url>=0A=
<description>=0A=
Eclipse Gemini Blueprint IO abstract classes. Provides Resource, =
ResourceLoader and ResourcePatternResolver for OSGi environments.=0A=
</description>=0A=
=0A=
=0A=
<properties>=0A=
<javadoc.loc>${basedir}/../docs/src/javadoc</javadoc.loc>=0A=
=
<spring.osgi.symbolic.name>${symName.prefix}.io</spring.osgi.symbolic.nam=
e>=0A=
<bundlor.enabled>true</bundlor.enabled>=0A=
</properties>=0A=
=0A=
<dependencies>=0A=
<dependency>=0A=
<groupId>org.eclipse.gemini.blueprint</groupId>=0A=
<artifactId>gemini-blueprint-mock</artifactId>=0A=
<scope>test</scope>=0A=
</dependency>=0A=
<dependency>=0A=
<groupId>org.springframework</groupId>=0A=
<artifactId>org.springframework.core</artifactId>=0A=
<scope>provided</scope>=0A=
</dependency> =0A=
</dependencies>=0A=
</project>=0A=

------=_NextPart_000_01E5_01CB2DC2.F1BE3170--

Report message to a moderator

Previous Topic:	Gemini Web Milestone 3
Next Topic:	Gemini artifactId naming inconsistent between sub-projects

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 23:36:21 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter