tycho-dev http://dev.eclipse.org/mhonarc/lists/tycho-dev/maillist.html tycho-dev en-us Tue, 14 May 2013 07:40:05 GMT Tue, 14 May 2013 07:40:05 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) tycho-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/tycho-dev/maillist.html Re: [tycho-dev] 0.18.0 release date? http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00914.html _______________________________________________ tycho-dev mailing list tycho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-dev opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=407972 please follow up there. Jan -----Original Message----- From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault Sent: Mittwoch, 1. Mai 2013 02:18 To: tycho-dev@xxxxxxxxxxx Subject: Re: [tycho-dev] 0.18.0 release date? I don't need a specific tycho fix, but rather I would need to have a new version of p2 to be consumed. More specifically I've committed a change to the publisher [1] that allows to identify product IUs. This simple change is key to make sure that p2 remediation mechanism does not remove the current product when something incompatible is installed (for an example of this situation see (https://bugs.eclipse.org/bugs/show_bug.cgi?id=406947)). We currently have a workaround in the platform build (https://bugs.eclipse.org/bugs/show_bug.cgi?id=406960) but generally speaking I think the issue is important enough that we want to make sure that we make the fix availble to the mass through tycho by the time Kepler is released. In addition to that, there is also the problem where Mac builds don't have an icon and there are people working on a fix in bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=406942. I realize that I've asked for a 0.18 build, but I'm completely happy with a 0.17.1 that just includes a new version of p2. [1] http://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=11c1ab663154efe0e0be72945607a9fe45ffc679 Pascal On Tue, April 30, 2013 10:55, Oberlies, Tobias wrote: > Usually, we do a release every four months [1], so this wouldn't be in > time for Kepler. But we could do an extra release for Kepler. > > What is the impact for you? Is there anything particular of the new things > in 0.18.0 [2] are you interested in? > > Regards > Tobias > > [1] http://wiki.eclipse.org/Tycho/Release_Notes > [2] > https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&resolution=FIXED&target_milestone=0.18.0&order=bug_id&list_id=5315632 > > >> -----Original Message----- >> From: tycho-dev-bounces@xxxxxxxxxxx >> [mailto:tycho-dev-bounces@xxxxxxxxxxx] >> On Behalf Of Pascal Rapicault >> Sent: Dienstag, 30. April 2013 15:50 >> To: tycho-dev@xxxxxxxxxxx >> Cc: platform-releng-dev@xxxxxxxxxxx >> Subject: [tycho-dev] 0.18.0 release date? >> >> Hi, >> >> I would like to know if 0.18.0 will be released in time to build Kepler >> with it? >> >> Thx >> >> Pascal >> >> _______________________________________________ >> tycho-dev mailing list >> tycho-dev@xxxxxxxxxxx >> https://dev.eclipse.org/mailman/listinfo/tycho-dev > _______________________________________________ tycho-dev mailing list tycho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-dev ]]> Tue, 14 May 2013 07:38:31 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00914.html jan.sievers@xxxxxxx (Sievers, Jan) Re: [tycho-dev] Tycho Gerrit Review Process: Some Questions http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00913.html we try to review every change unless considered really trivial. That said, there is no hard-and-fast "must review all changes" rule. we are using gerrit for tycho since April 2012. Some of the team members have been using gerrit for several years in other... >1) Is this ture, i.e. is the review policy rigorous? Or are there >changes to the repository that can go un-reviewed? we try to review every change unless considered really trivial. That said, there is no hard-and-fast "must review all changes" rule. >2) Since when do you use code review? we are using gerrit for tycho since April 2012. Some of the team members have been using gerrit for several years in other projects. >3) I noticed there can arise changes without a linked bugzilla id. >When/why does this happen? should not happen unless the change is considered really trivial/non-functional (such as "reformat/fix line endings" or similar). That said, to err is human. Regards, Jan ]]> Mon, 13 May 2013 07:55:02 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00913.html jan.sievers@xxxxxxx (Sievers, Jan) Re: [tycho-dev] Tycho Gerrit Review Process: Some Questions http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00912.html See inline. Trivial changes can go in without offering them for review. Also, we don't require a review - only that committers offer the chance for review. This is typically done by proposing a change in Gerrit and by waiting three days before submitting i... See inline. > -----Original Message----- > From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] > On Behalf Of Moritz Beller > Sent: Freitag, 10. Mai 2013 14:42 > To: tycho-dev@xxxxxxxxxxx > Subject: [tycho-dev] Tycho Gerrit Review Process: Some Questions > > Hi there! > > I am a computer scientist at Technical University of Munich. My field of > research is Code Reviews. My research questions focus around which types > of defects are usually found during code reviews in open source > projects. For this, I want to set-up an empirical study with open source > systems employing Gerrit Code Reviews. Tycho could be one of them. > paulweb515 in #eclipse-dev pin-pointed me to look at Tycho. > > A quick scan through the code base of Tycho suggested to me that code > reviews are mandatory for every commit. Before I could include Tycho > into the study I have a few questions: > > 1) Is this ture, i.e. is the review policy rigorous? Or are there > changes to the repository that can go un-reviewed? Trivial changes can go in without offering them for review. Also, we don't require a review - only that committers offer the chance for review. This is typically done by proposing a change in Gerrit and by waiting three days before submitting it. BTW, this are our Gerrit permissions: https://git.eclipse.org/r/#/admin/projects/tycho/org.eclipse.tycho,access. > 2) Since when do you use code review? Since April 2012 -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=371620 > 3) I noticed there can arise changes without a linked bugzilla id. > When/why does this happen? Trivial changes like formatting or pure refactoring changes don't need a corresponding bug. If there is no functional change, there is no need to have an entry in the issue&change tracker. > Thanks a lot for helping me. > > Best > Moritz > Regards Tobias ]]> Mon, 13 May 2013 06:53:59 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00912.html tobias.oberlies@xxxxxxx (Oberlies, Tobias) [tycho-dev] Tycho Gerrit Review Process: Some Questions http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00911.html Hi there! I am a computer scientist at Technical University of Munich. My field of research is Code Reviews. My research questions focus around which types of defects are usually found during code reviews in open source projects. For this, I want to set-up... Hi there!
I am a computer scientist at Technical University of Munich. My field of research is Code Reviews. My research questions focus around which types of defects are usually found during code reviews in open source projects. For this, I want to set-up an empirical study with open source systems employing Gerrit Code Reviews. Tycho could be one of them. paulweb515 in #eclipse-dev pin-pointed me to look at Tycho.

A quick scan through the code base of Tycho suggested to me that code reviews are mandatory for every commit. Before I could include Tycho into the study I have a few questions:

1) Is this ture, i.e. is the review policy rigorous? Or are there changes to the repository that can go un-reviewed?
2) Since when do you use code review?
3) I noticed there can arise changes without a linked bugzilla id. When/why does this happen?

Thanks a lot for helping me.

Best
Moritz





]]> Fri, 10 May 2013 12:41:50 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00911.html m.o.m.o@xxxxxxx (Moritz Beller) Re: [tycho-dev] How to get P2 dependency URL with tycho. http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00910.html Hi Tobias    Thank you very much! I archived all my targets. You hint was very valuable. You show me where is no solution. That significantly narrow my field of decisions and I save huge chunk of time. I just rewrote a little DefaultEquinoxEmbedder and the... Hi Tobias
    Thank you very much! I archived all my targets. You hint was very valuable. You show me where is no solution. That significantly narrow my field of decisions and I save huge chunk of time.
I just rewrote a little DefaultEquinoxEmbedder and then right after resolution process:

    val agentClass = equinox.getClass.getClassLoader().loadClass("org.eclipse.equinox.p2.core.IProvisioningAgent")
    val remoteAgent = equinox.getService(agentClass).asInstanceOf[{ def getService(serviceName: String): AnyRef }]
    val remoteMetadataRepositoryManager = remoteAgent.getService(IMetadataRepositoryManager.SERVICE_NAME).asInstanceOf[IMetadataRepositoryManager]
    val remoteArtifactRepositoryManager = remoteAgent.getService(IArtifactRepositoryManager.SERVICE_NAME).asInstanceOf[IArtifactRepositoryManager]
    val repos = remoteArtifactRepositoryManager.getKnownRepositories(IRepositoryManager.REPOSITORIES_ALL)
    for (i <- repos) {
      val x = remoteArtifactRepositoryManager.loadRepository(i, null) <---- Hurray!!! Bingo. All bundles per URL + bundles with source code as a bonus!!! Wow
      System.err.println("!!!" + x)
    }

Only few lines, splendid. I will buy to you your favorite alcohol drink (or cup of coffee, tea, chai, cocoa, etc.) if there will be occasion ;-)

Thank you for help.
Alexey


2013/5/6 Oberlies, Tobias <tobias.oberlies@xxxxxxx>

From your code snippet, it seems that you already got the shortest way to make Tycho download artifacts – by doing the full target platform & resolve cycle.

 

But this will probably improve in the near future: I need to simplify things for Tycho (https://bugs.eclipse.org/bugs/show_bug.cgi?id=393004 ), and you may be able to directly use the new MirroringArtifactProvider to simply download the artifacts you want. Note that all this isn’t in master yet, but you can see a prototype in Gerrit (see link in the bug). I’ll probably also post an updated patch in the next couple of days.

 

Regards

Tobias

 

 

From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Alexey Aksenov
Sent: Montag, 6. Mai 2013 15:10
To: Tycho developers list
Subject: Re: [tycho-dev] How to get P2 dependency URL with tycho.

 

Hi Tobias,

    Thank you for interest in my problem. My little application is not OSGi. Tycho team already do some work for integration OSGi with "the real world of classpath hell". IMHO most effective way is to reuse components, not to create my own. My "resolve" function already download artifacts. I just want to reduce it functionality a bit.
Some people write there own class loaders on second day. But I know that this is not fun for them. Sure that they have a lot of other problems.
    I must to pass URLs to external resolution mechanism. Please just point me to the right chunk of source code in Tycho infrastructure. I may spent a lot of time to read it all page by page.

My thankfulness will be unlimited. Within reasonable limits of course ;-)

Thank you,
Alexey

 

2013/5/6 Oberlies, Tobias <tobias.oberlies@xxxxxxx>

Hi Alexey,

 

I don’t know if writing your own resolver is really the next step you want to do after having done the Hello World example. This is a bit like writing your own class loader on the second day of a Java beginners course… ;-)

 

So if you are only interested in downloading p2 artifacts to the Maven repository? Why don’t you just trigger a Tycho build to do this for you, and then do whatever you like with the artifacts cached by Tycho?

 

Regards

Tobias

 

 

From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Alexey Aksenov
Sent: Montag, 6. Mai 2013 14:39
To: tycho-dev@xxxxxxxxxxx
Subject: [tycho-dev] How to get P2 dependency URL with tycho.

 

Hi All.

I read tycho helloworld documentation and write my own resolver. I run maven as embedded library. This way allow to download P2 bundles to .m2 directory :-)
The problem is I don't want to download dependency. I want to know dependency URL!?? Huh!
I resolve P2 dependency with the following simple function (I like Scala, but this is not significant):

def resolve2(maven: Maven, log: Logger) {
    val equinox = maven.lookup(classOf[EquinoxServiceFactory])
    val resolverFactory = equinox.getService(classOf[P2ResolverFactory])
    val targetPlatformBuilder = resolverFactory.createTargetPlatformBuilder(
      new ExecutionEnvironmentConfigurationStub("JavaSE-1.6"))
    targetPlatformBuilder.addP2Repository(new MavenRepositoryLocation("test", new URL("http://eclipse.ialto.com/eclipse/updates/4.2/R-4.2.1-201209141800/").toURI))
    val targetPlatform = targetPlatformBuilder.buildTargetPlatform()
    val resolver = resolverFactory.createResolver(new MavenLoggerAdapter(maven.plexus.getLogger, true))
    val result = resolver.resolveDependencies(targetPlatform, null)
    System.err.println("!!!" + result)
  }

There is a lot of components involved in the process. So, I need a little hint that point me to the right direction. What is class (or package) responsible for a dependency URL resolution/collection?

Regards,
Alexey


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

 


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


]]> Mon, 06 May 2013 22:13:40 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00910.html alexey.ezh@xxxxxxx (Alexey Aksenov) Re: [tycho-dev] How to get P2 dependency URL with tycho. http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00909.html From your code snippet, it seems that you already got the shortest way to make Tycho download artifacts &#8211; by doing the full target platform &amp; resolve cycle. But this will probably improve in the near future: I need to simplify things for Tycho (https://...

From your code snippet, it seems that you already got the shortest way to make Tycho download artifacts – by doing the full target platform & resolve cycle.

 

But this will probably improve in the near future: I need to simplify things for Tycho (https://bugs.eclipse.org/bugs/show_bug.cgi?id=393004 ), and you may be able to directly use the new MirroringArtifactProvider to simply download the artifacts you want. Note that all this isn’t in master yet, but you can see a prototype in Gerrit (see link in the bug). I’ll probably also post an updated patch in the next couple of days.

 

Regards

Tobias

 

 

From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Alexey Aksenov
Sent: Montag, 6. Mai 2013 15:10
To: Tycho developers list
Subject: Re: [tycho-dev] How to get P2 dependency URL with tycho.

 

Hi Tobias,

    Thank you for interest in my problem. My little application is not OSGi. Tycho team already do some work for integration OSGi with "the real world of classpath hell". IMHO most effective way is to reuse components, not to create my own. My "resolve" function already download artifacts. I just want to reduce it functionality a bit.
Some people write there own class loaders on second day. But I know that this is not fun for them. Sure that they have a lot of other problems.
    I must to pass URLs to external resolution mechanism. Please just point me to the right chunk of source code in Tycho infrastructure. I may spent a lot of time to read it all page by page.

My thankfulness will be unlimited. Within reasonable limits of course ;-)

Thank you,
Alexey

 

2013/5/6 Oberlies, Tobias <tobias.oberlies@xxxxxxx>

Hi Alexey,

 

I don’t know if writing your own resolver is really the next step you want to do after having done the Hello World example. This is a bit like writing your own class loader on the second day of a Java beginners course… ;-)

 

So if you are only interested in downloading p2 artifacts to the Maven repository? Why don’t you just trigger a Tycho build to do this for you, and then do whatever you like with the artifacts cached by Tycho?

 

Regards

Tobias

 

 

From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Alexey Aksenov
Sent: Montag, 6. Mai 2013 14:39
To: tycho-dev@xxxxxxxxxxx
Subject: [tycho-dev] How to get P2 dependency URL with tycho.

 

Hi All.

I read tycho helloworld documentation and write my own resolver. I run maven as embedded library. This way allow to download P2 bundles to .m2 directory :-)
The problem is I don't want to download dependency. I want to know dependency URL!?? Huh!
I resolve P2 dependency with the following simple function (I like Scala, but this is not significant):

def resolve2(maven: Maven, log: Logger) {
    val equinox = maven.lookup(classOf[EquinoxServiceFactory])
    val resolverFactory = equinox.getService(classOf[P2ResolverFactory])
    val targetPlatformBuilder = resolverFactory.createTargetPlatformBuilder(
      new ExecutionEnvironmentConfigurationStub("JavaSE-1.6"))
    targetPlatformBuilder.addP2Repository(new MavenRepositoryLocation("test", new URL("http://eclipse.ialto.com/eclipse/updates/4.2/R-4.2.1-201209141800/").toURI))
    val targetPlatform = targetPlatformBuilder.buildTargetPlatform()
    val resolver = resolverFactory.createResolver(new MavenLoggerAdapter(maven.plexus.getLogger, true))
    val result = resolver.resolveDependencies(targetPlatform, null)
    System.err.println("!!!" + result)
  }

There is a lot of components involved in the process. So, I need a little hint that point me to the right direction. What is class (or package) responsible for a dependency URL resolution/collection?

Regards,
Alexey


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

 

]]> Mon, 06 May 2013 13:47:26 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00909.html tobias.oberlies@xxxxxxx (Oberlies, Tobias) Re: [tycho-dev] How to get P2 dependency URL with tycho. http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00908.html Hi Tobias,&#xA0;&#xA0;&#xA0; Thank you for interest in my problem. My little application is not OSGi. Tycho team already do some work for integration OSGi with &quot;the real world of classpath hell&quot;. IMHO most effective way is to reuse components, not to create my own. My uo... Hi Tobias,

    Thank you for interest in my problem. My little application is not OSGi. Tycho team already do some work for integration OSGi with "the real world of classpath hell". IMHO most effective way is to reuse components, not to create my own. My "resolve" function already download artifacts. I just want to reduce it functionality a bit.
Some people write there own class loaders on second day. But I know that this is not fun for them. Sure that they have a lot of other problems.
    I must to pass URLs to external resolution mechanism. Please just point me to the right chunk of source code in Tycho infrastructure. I may spent a lot of time to read it all page by page.

My thankfulness will be unlimited. Within reasonable limits of course ;-)

Thank you,
Alexey


2013/5/6 Oberlies, Tobias <tobias.oberlies@xxxxxxx>

Hi Alexey,

 

I don’t know if writing your own resolver is really the next step you want to do after having done the Hello World example. This is a bit like writing your own class loader on the second day of a Java beginners course… ;-)

 

So if you are only interested in downloading p2 artifacts to the Maven repository? Why don’t you just trigger a Tycho build to do this for you, and then do whatever you like with the artifacts cached by Tycho?

 

Regards

Tobias

 

 

From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Alexey Aksenov
Sent: Montag, 6. Mai 2013 14:39
To: tycho-dev@xxxxxxxxxxx
Subject: [tycho-dev] How to get P2 dependency URL with tycho.

 

Hi All.

I read tycho helloworld documentation and write my own resolver. I run maven as embedded library. This way allow to download P2 bundles to .m2 directory :-)
The problem is I don't want to download dependency. I want to know dependency URL!?? Huh!
I resolve P2 dependency with the following simple function (I like Scala, but this is not significant):

def resolve2(maven: Maven, log: Logger) {
    val equinox = maven.lookup(classOf[EquinoxServiceFactory])
    val resolverFactory = equinox.getService(classOf[P2ResolverFactory])
    val targetPlatformBuilder = resolverFactory.createTargetPlatformBuilder(
      new ExecutionEnvironmentConfigurationStub("JavaSE-1.6"))
    targetPlatformBuilder.addP2Repository(new MavenRepositoryLocation("test", new URL("http://eclipse.ialto.com/eclipse/updates/4.2/R-4.2.1-201209141800/").toURI))
    val targetPlatform = targetPlatformBuilder.buildTargetPlatform()
    val resolver = resolverFactory.createResolver(new MavenLoggerAdapter(maven.plexus.getLogger, true))
    val result = resolver.resolveDependencies(targetPlatform, null)
    System.err.println("!!!" + result)
  }

There is a lot of components involved in the process. So, I need a little hint that point me to the right direction. What is class (or package) responsible for a dependency URL resolution/collection?

Regards,
Alexey


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


]]> Mon, 06 May 2013 13:10:25 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00908.html alexey.ezh@xxxxxxx (Alexey Aksenov) Re: [tycho-dev] How to get P2 dependency URL with tycho. http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00907.html Hi Alexey, I don&#8217;t know if writing your own resolver is really the next step you want to do after having done the Hello World example. This is a bit like writing your own class loader on the second day of a Java beginners course&#8230; ;-) bsp; So if you are ...

Hi Alexey,

 

I don’t know if writing your own resolver is really the next step you want to do after having done the Hello World example. This is a bit like writing your own class loader on the second day of a Java beginners course… ;-)

 

So if you are only interested in downloading p2 artifacts to the Maven repository? Why don’t you just trigger a Tycho build to do this for you, and then do whatever you like with the artifacts cached by Tycho?

 

Regards

Tobias

 

 

From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Alexey Aksenov
Sent: Montag, 6. Mai 2013 14:39
To: tycho-dev@xxxxxxxxxxx
Subject: [tycho-dev] How to get P2 dependency URL with tycho.

 

Hi All.

I read tycho helloworld documentation and write my own resolver. I run maven as embedded library. This way allow to download P2 bundles to .m2 directory :-)
The problem is I don't want to download dependency. I want to know dependency URL!?? Huh!
I resolve P2 dependency with the following simple function (I like Scala, but this is not significant):

def resolve2(maven: Maven, log: Logger) {
    val equinox = maven.lookup(classOf[EquinoxServiceFactory])
    val resolverFactory = equinox.getService(classOf[P2ResolverFactory])
    val targetPlatformBuilder = resolverFactory.createTargetPlatformBuilder(
      new ExecutionEnvironmentConfigurationStub("JavaSE-1.6"))
    targetPlatformBuilder.addP2Repository(new MavenRepositoryLocation("test", new URL("http://eclipse.ialto.com/eclipse/updates/4.2/R-4.2.1-201209141800/").toURI))
    val targetPlatform = targetPlatformBuilder.buildTargetPlatform()
    val resolver = resolverFactory.createResolver(new MavenLoggerAdapter(maven.plexus.getLogger, true))
    val result = resolver.resolveDependencies(targetPlatform, null)
    System.err.println("!!!" + result)
  }

There is a lot of components involved in the process. So, I need a little hint that point me to the right direction. What is class (or package) responsible for a dependency URL resolution/collection?

Regards,
Alexey

]]> Mon, 06 May 2013 12:51:03 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00907.html tobias.oberlies@xxxxxxx (Oberlies, Tobias) [tycho-dev] How to get P2 dependency URL with tycho. http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00906.html Hi All.I read tycho helloworld documentation and write my own resolver. I run maven as embedded library. This way allow to download P2 bundles to .m2 directory :-)The problem is I don&#39;t want to download dependency. I want to know dependency URL!?? Huh! I r... Hi All.

I read tycho helloworld documentation and write my own resolver. I run maven as embedded library. This way allow to download P2 bundles to .m2 directory :-)
The problem is I don't want to download dependency. I want to know dependency URL!?? Huh!
I resolve P2 dependency with the following simple function (I like Scala, but this is not significant):

def resolve2(maven: Maven, log: Logger) {
    val equinox = maven.lookup(classOf[EquinoxServiceFactory])
    val resolverFactory = equinox.getService(classOf[P2ResolverFactory])
    val targetPlatformBuilder = resolverFactory.createTargetPlatformBuilder(
      new ExecutionEnvironmentConfigurationStub("JavaSE-1.6"))
    targetPlatformBuilder.addP2Repository(new MavenRepositoryLocation("test", new URL("http://eclipse.ialto.com/eclipse/updates/4.2/R-4.2.1-201209141800/").toURI))
    val targetPlatform = targetPlatformBuilder.buildTargetPlatform()
    val resolver = resolverFactory.createResolver(new MavenLoggerAdapter(maven.plexus.getLogger, true))
    val result = resolver.resolveDependencies(targetPlatform, null)
    System.err.println("!!!" + result)
  }

There is a lot of components involved in the process. So, I need a little hint that point me to the right direction. What is class (or package) responsible for a dependency URL resolution/collection?

Regards,
Alexey
]]> Mon, 06 May 2013 12:38:57 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00906.html alexey.ezh@xxxxxxx (Alexey Aksenov) Re: [tycho-dev] 0.18.0 release date? http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00905.html _______________________________________________ tycho-dev mailing list tycho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-dev there are other patches for the platform build of the kepler release pending in the meantime [1]. we do need a tycho release in time for the final kepler build for build reproducibility reasons. things are still moving now and I don't want to do a release only to find out there's another last minute stopper for the eclipse platform build. Currently I'm thinking it's best for the platform build to move to 0.18.0-SNAPSHOT and we'll do a tycho release from 0.18.0-SNAPSHOT as late as possible before the final kepler build. What do you think? Jan [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=406465 -----Original Message----- From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault Sent: Mittwoch, 1. Mai 2013 02:18 To: tycho-dev@xxxxxxxxxxx Subject: Re: [tycho-dev] 0.18.0 release date? I don't need a specific tycho fix, but rather I would need to have a new version of p2 to be consumed. More specifically I've committed a change to the publisher [1] that allows to identify product IUs. This simple change is key to make sure that p2 remediation mechanism does not remove the current product when something incompatible is installed (for an example of this situation see (https://bugs.eclipse.org/bugs/show_bug.cgi?id=406947)). We currently have a workaround in the platform build (https://bugs.eclipse.org/bugs/show_bug.cgi?id=406960) but generally speaking I think the issue is important enough that we want to make sure that we make the fix availble to the mass through tycho by the time Kepler is released. In addition to that, there is also the problem where Mac builds don't have an icon and there are people working on a fix in bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=406942. I realize that I've asked for a 0.18 build, but I'm completely happy with a 0.17.1 that just includes a new version of p2. [1] http://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=11c1ab663154efe0e0be72945607a9fe45ffc679 Pascal On Tue, April 30, 2013 10:55, Oberlies, Tobias wrote: > Usually, we do a release every four months [1], so this wouldn't be in > time for Kepler. But we could do an extra release for Kepler. > > What is the impact for you? Is there anything particular of the new things > in 0.18.0 [2] are you interested in? > > Regards > Tobias > > [1] http://wiki.eclipse.org/Tycho/Release_Notes > [2] > https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&product=Tycho&query_format=advanced&resolution=FIXED&target_milestone=0.18.0&order=bug_id&list_id=5315632 > > >> -----Original Message----- >> From: tycho-dev-bounces@xxxxxxxxxxx >> [mailto:tycho-dev-bounces@xxxxxxxxxxx] >> On Behalf Of Pascal Rapicault >> Sent: Dienstag, 30. April 2013 15:50 >> To: tycho-dev@xxxxxxxxxxx >> Cc: platform-releng-dev@xxxxxxxxxxx >> Subject: [tycho-dev] 0.18.0 release date? >> >> Hi, >> >> I would like to know if 0.18.0 will be released in time to build Kepler >> with it? >> >> Thx >> >> Pascal >> >> _______________________________________________ >> tycho-dev mailing list >> tycho-dev@xxxxxxxxxxx >> https://dev.eclipse.org/mailman/listinfo/tycho-dev > _______________________________________________ tycho-dev mailing list tycho-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-dev ]]> Fri, 03 May 2013 07:15:14 GMT http://dev.eclipse.org/mhonarc/lists/tycho-dev/msg00905.html jan.sievers@xxxxxxx (Sievers, Jan)