Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] tycho 0.11.0 always downloading content.xml and artifacts.xml from local p2 helios mirror


Hi,

I consider p2 repositories as generated content, therefore i do not check them in in version control. 
In my target file i use only remote locations that points to p2 mirrors on an internal webserver.

Repositories from external projects (for example the eclipse helios repository, or the eclipse orbit repository) are mirrored on that webserver. 
Repositories from internal projects are mirrored to that webserver in the build process. The successive repositories of a project are grouped in a composite repository.

About best practices: i always look for them, but in the end there are many possibilities that cannot be covered in best practices. I look at the situation and use the combination of tools that works best for that situation.
While using remote locations in my target file works for my current situation, it won't work if i have no access to that remote location (f.e. at home). 

Regards,
Davy



Date: Tue, 3 May 2011 18:05:27 +0200
From: dimo.public@xxxxxxxxxxxxxx
To: tycho-user@xxxxxxxxxxx
Subject: Re: [tycho-user] tycho 0.11.0 always downloading content.xml and artifacts.xml from local p2 helios mirror

Hi Davy,

I also have a very small module consisting basically of a pom and the .target definition.

The question is what do you define in your .target:
* In https://github.com/sonatype/sonatype-tycho/blob/master/tycho-its/projects/TYCHO59targetDefinition/target-platform/platform.target we reference a local (right?) repository located at repositories/e342. How do you make that repository available to all developers: you either check it in version control or have another way of sharing it. What is the best practice here?

* In my target definition I use a remote location pointing to a project wide nexus p2 repository mirror of helios. This way each developer gets it from a common location which is under our control. I assumed that would be the best practice but seem to not be quite right.

Best regards,
Dimo

On Tue, May 3, 2011 at 11:04 AM, Davy Meers <davymeers@xxxxxxxxxxx> wrote:
Hi Dimo,

I use a maven project that contains the .target file. Since it is a project like any other it is put into version control.


Regards,
Davy


Date: Tue, 3 May 2011 10:49:46 +0200
From: dimo.public@xxxxxxxxxxxxxx
To: tycho-user@xxxxxxxxxxx
Subject: Re: [tycho-user] tycho 0.11.0 always downloading content.xml and artifacts.xml from local p2 helios mirror


Hi Vincent,

Thank you for the fast response!

We are currently targeting only one platform so it should be possible. I did not really know however how to build it and also it would require us to keep it under version control which I would not like to do.

Is that the normal practice with eclipse RCP and tycho - to keep the target platform(s) in version control? If not, how do you distribute the target platform to all developers?

Best regards,
Dimo

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

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



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

Back to the top