Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [gemini-dev] Release 2.0.0.M02 of gemini-blueprint

Hi Dmitry

 

Thank you for providing the M02 artifact, obtaining it from that location does work. However, what about moving to the official eclipse maven repos (http://wiki.eclipse.org/Services/Nexus)  ?

 

Regards,

Olaf

 

From: Dmitry Sklyut [mailto:dmitry@xxxxxxxxxxx]
Sent: Montag, 30. Juni 2014 23:26
To: Gemini and sub-projects developer discussions; Olaf Otto
Subject: Re: [gemini-dev] Release 2.0.0.M02 of gemini-blueprint

 

Olaf,

 

 

<repository>
      <id>eclipse-gemini</id>
      <name>Eclipse Gemini Maven repository</name>
      <url>http://download.eclipse.org/gemini/mvn/</url>
</repository>

 

Let me know if they are working out for you.  Had to clean up 2.0.0.M2 tagged pom files a bit to get a build to work.

 

-- 
Dmitry Sklyut
Sent with Airmail

 

On June 24, 2014 at 3:33:37 AM, Olaf Otto (olaf@xxxxxxx) wrote:

Hi Dmitry

 

One more thing: It appears maven artifacts are disappearing from the Spring EBR at the moment. At least, I can no longer obtain the M2 release from this location as a maven dependency. Only ivy dependencies are working at the moment.

 

Could you provide the 2.0.0.M02 build to the ecplise repo? I am in very urgent need of that artifact being available from a public repository.

 

Thanks and regards,

Olaf

 

From: gemini-dev-bounces@xxxxxxxxxxx [mailto:gemini-dev-bounces@xxxxxxxxxxx] On Behalf Of Dmitry Sklyut
Sent: Montag, 16. Juni 2014 21:48
To: Gemini and sub-projects developer discussions
Subject: Re: [gemini-dev] Release 2.0.0 of gemini-blueprint

 

Olaf,

 

The build is already in publishing SNAPSHOTS to repo.eclipse.org.

 

My main concern about releasing 2.0 is our inability to easily upgrade spring framework related artifacts. Spring EBR is dead.  Eclipse EBR is focused only on Eclipse artifacts only (if I understand it’s chapter properly).

 

I have finished upgrading all of the frameworks to R5  compliant releases.

Next step is to remove deprecated pieces, like PackageAdmin and support for ancient versions of frameworks.

 

I would like to resolve the spring framework dependency issue prior to releasing of 2.0.

 

What are your thoughts?

 

 

Kind Regards,

 

-- 
Dmitry Sklyut
Sent with Airmail

 

On June 10, 2014 at 9:54:47 AM, Olaf Otto (olaf@xxxxxxx) wrote:

Hi all,

 

I was wondering which issues are outstanding in order to ship release 2.0.0. Looking at the bugs (https://bugs.eclipse.org/bugs/buglist.cgi?component=Core&list_id=9328345&product=Gemini.Blueprint&resolution=---), I found nothing that looks like a blocker (but some that we may close / wontfix). I feel it is crucial to release to the eclipse maven repo (https://repo.eclipse.org/index.html) since our old releases are in the spring EBR which is scheduled for EOL.

 

@Dmitry, anything I could help with to get the release on the road?

 

Kind regards,

Olaf

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

Back to the top