Hello,
There is a major regression in Eclipse batch compiler in the current
4.7.x branch compared to 4.7.1, which essentially breaks all users who
run on java8 and do annotation processing (more info in [1]). I'd like
to ask to backport https://git.eclipse.org/r/#/c/112386/ and can propose
a chang
Interesting. It now works when I am on US-based VPN, but still does not
work through a Canadian ISP. Both didn't work earlier today.
--
Regards,
Igor
On Wed, Aug 26, 2015, at 08:24 AM, Matthias Sohn wrote:
> On Wed, Aug 26, 2015 at 2:13 PM, Igor Fedorenko wrote:
>> Is
Is it me, or http://git.eclipse.org/c/ does not work today? The search
always says "No repositories found". Clicking on any repository in the
list does not do anything useful. Seems similar to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=445288 reported awhile
back, which was marked closed/fixed w
I am pretty sure we are not allowed to collect usage data. Wayne still
can't decide the policy around this [1]. I have some opensource code for
out-of-eclipse usage collection which I use with my m2e extensions, if
you are interested.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=413169
--
R
You can use jetty to create in-process http proxy servers. There is
helper for this in m2e [1] and I think Tycho has something similar too.
There is also MockWebServer from Square [2], which arguably gives you
finer control over your test server behaviour. We use it to test some
aspects of Aether
Just to clarify, m2e is quite happy with guava 15 included in sim rel
and we will need to validate if guava 18 breaks anything. m2e does plan
to ship separate guava 18 as part of embedded maven runtime, but this
copy is not exported to OSGi and should not interfere with guava
used by other OSGi bu
This is getting off-topic, but I think we should plan to move to java 8
for the next release after mars. If we start talking about this now and
announce this as part of mars release, I think this gives users plenty
of time to prepare and less excuse for grumbling (although I imagine
there still be
Just a heads up, m2e will miss CQ submission deadline. We are still
waiting for Maven 3.2.6 release we plan to embed.
--
Regards,
Igor
On 2015-02-09 13:30, Wayne Beaton wrote:
Greetings. *If your project is participating in Mars, please read this
entire message.*
The *February 13th deadline fo
p2 only provides approximation of osgi dependency resolution rules. it
does not honour mandatory attributes, bundle-symbolic-name and
bundle-version Import-Package directives, and probably more.
I've introduced dependency-resolution parameter to
workaround this in Tycho, but to make this work du
14-10-08, 9:27, Mat Booth wrote:
- Original Message -
From: "Igor Fedorenko"
To: cross-project-issues-dev@eclipse.org
Sent: Wednesday, 8 October, 2014 12:38:10 PM
Subject: Re: [cross-project-issues-dev] Limiting GTK versions supported by SWT
or SWT call for help
What major dis
What major distribution still stuck with GTK2? Aren't they all on GTK3
already?
--
Regards,
Igor
On 2014-10-08, 2:40, Aleksandar Kurtakov wrote:
- Original Message -
From: "Marc-André Laperle"
To: "Cross project issues"
Sent: Wednesday, October 8, 2014 6:25:14 AM
Subject: Re: [cross-
On 2014-10-07, 11:15, Aleksandar Kurtakov wrote:
Please reply to this thread and let us know what your thoughts are. It
would be very useful for us to also know which versions of GTK+ are being
used widely and what is the minimum required version that you need support
for from future releases o
e-dev/msg01685.html>
--
Regards,
Igor
On 2014-09-02, 10:52, Wayne Beaton wrote:
There were 26 commits in August.
Why no new release?
Wayne
On 29/08/14 07:25 AM, Igor Fedorenko wrote:
m2e will participate in Mars simultaneous release. m2e
25 AM, Igor Fedorenko wrote:
m2e will participate in Mars simultaneous release. m2e offset is +2,
iirc. We'll contribute the same build to Mars as we did in Luna.
https://projects.eclipse.org/projects/technology.m2e/releases/1.5.0
--
Regards,
Igor
___
m2e will participate in Mars simultaneous release. m2e offset is +2,
iirc. We'll contribute the same build to Mars as we did in Luna.
https://projects.eclipse.org/projects/technology.m2e/releases/1.5.0
--
Regards,
Igor
___
cross-project-issues-dev mail
FWIW, we build m2e against simrel repository and don't have any problems.
http://ci.tesla.io:8080/view/m2e/job/m2eclipse-core/
--
Regards,
Igor
On 2014-06-27, 10:27, Max Rydahl Andersen wrote:
On 26 Jun 2014, at 10:49, Doug Schaefer wrote:
We build directly against the Eclipse one. Does that
s/staging, and we're fine with that. We've probably spent more time on
this thread than it does to change your target to point at it.
Doug.
From: cross-project-issues-dev-boun...@eclipse.org
[cross-project-issues-dev-boun...@eclipse.o
So it is okay to "release" all M and most RC builds as they become
available but the final RC needs special treatment because we do not
want to dull the excitement?
--
Regards,
Igor
On 2014-06-19, 10:02, Denis Roy wrote:
On 06/19/2014 09:28 AM, Igor Fedorenko wrote:
Personally, thou
y common for many projects (such as Tycho) to be
available in a "staging" location for a period, before officially moving
to the "released" location.
Perhaps this FAQ would help?
http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#What.27s_the_best_way_to_test_with_the_sta
Little late to the party, but I'd like to suggest adding RC4 to Luna
composite and making this part of symrel process going forward. By
"hiding" RC4 under obscure URL we artificially limit amount of testing
it gets and make it harder for downstream projects validate their code
will still work year
This is tracked as Tycho
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436159
Either use Platform build with 435888 fixed or switch to Tycho
0.21 snapshot, which should be more tolerate to exceptions during test
framework shutdown.
--
Regards,
Igor
On 2014-06-06, 12:17, Thomas Watson wrote:
Th
On 2014-06-02, 5:31, Ed Willink wrote:
a) Guava must not be exported and so avoid OSGI class loader confusion.
- API tooling could warn if any non-singleton plugin is exported.
b) Requirements to load Guava classes must not be exported
- API tooling could warn if a class in a non-singleton plu
David,
With 60+ comments on the bug you linked, it's hard to understand what
individual projects are expected to do. What license feature are we
supposed to use now? Is it available from Luna symrel composite repo
already?
--
Regards,
Igor
On 2014-04-24, 4:41, David M Williams wrote:
I'm sure
We are not allowed to collect any usage stats, so "gut feeling" is the
most scientific tool available to us.
Sorry, could not resist.
--
Regards,
Igor
On 2014-03-27, 19:26, Doug Schaefer wrote:
I understand your frustration. I think your efforts would be better
spent though trying to convince
Are you talking about separate update site with java 8 patches for
kepler or full-blown release?
In any case, m2e does not plan to participate. Anyone who wants to use
m2e with java 8 support on kepler will have to install m2e 1.5
milestone/snapshot build from m2e specific repository.
--
Regards
I am not sure I understand what you mean by "Artifacts ... are deployed
automatically to our Maven repository." Last I checked, Tycho did not
fully support resolution of OSGi/P2 dependencies from Maven
repositories. Can you explain what artifacts are deployed to and how
they are consumed from the
Do you need to do any "real" migration from 1.x to 2.x, for example
workspace data format upgrades and the like, or it is purely feature
rename? I vaguely remember there was way to tell p2 that one installable
unit replaces another, which directly supports your feature rename scenario.
--
Regards
+3 (in consideration of m2e-wtp)?
Wayne
On 12/18/2013 03:02 PM, Igor Fedorenko wrote:
I created release record. You can find release plan.xml in our site git
repository
http://git.eclipse.org/c/www.eclipse.org/m2e.git/tree/plan.xml?id=6c18b3cf58143f5f462f2f3b601ef2996887ef07
--
Regards,
Igor
can reference. That release
record needs to include plan information.
http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29
Wayne
On 12/18/2013 07:23 AM, Igor Fedorenko wrote:
@Wayne please update your records that m2e will participate in luna,
offset is +3
... and to make things even more fun, there does not appear to be a way
to "close" pending pull requests.
--
Regards,
Igor
On 12/18/2013, 5:19, Mickael Istria wrote:
Actually, it appears that there is no way to disable pull requests, even
for a mirror.
http://laurent.bachelier.name/2012/05/gith
discussed with Janet and team, but from my
experience they will try to help as good as they can.
Thanks,
Markus
On Mon, Dec 16, 2013 at 7:20 PM, Igor Fedorenko mailto:i...@ifedorenko.com>> wrote:
What is your suggestion?
BTW, I didn't even realize m2e was part of RCP/RAP pack
Wayne,
Which parts of m2e are required to carry "incubating" label, only
feature and bundles that *include* Aether and Sisu or everything that
makes use of Aether and Sisu (which is entire m2e)? I couldn't find any
wiki that explains how to brand projects that consume incubating components.
--
R
on" label on my
package, and I am sure that the Java and Java EE package maintainers
have a similar opinion.
Thanks,
Markus
On Mon, Dec 16, 2013 at 7:13 PM, Igor Fedorenko mailto:i...@ifedorenko.com>> wrote:
On 12/16/2013, 12:45, Wayne Beaton wrote:
The submission deadline i
On 12/16/2013, 12:45, Wayne Beaton wrote:
The submission deadline is the deadline for all CQs. The May deadline
was for IP log submission.
I agree that if Sisu and Aether have both been adopted by a release
version of Maven, that this is a pretty clear indication that they are
mature technolog
Wasn't there another deadline in February for new CQ submissions?
--
Regards,
Igor
On 12/16/2013, 9:36, Matthias Sohn wrote:
On Mon, Dec 16, 2013 at 1:17 PM, Igor Fedorenko mailto:i...@ifedorenko.com>> wrote:
On 12/16/2013, 4:16, Mike Milinkovich wrote:
On 15/12/20
On 12/16/2013, 4:16, Mike Milinkovich wrote:
On 15/12/2013 11:06 PM, Igor Fedorenko wrote:
Problem is, maven 3.1.x includes Eclipse Aether and
Eclipse Sisu binaries, both currently under incubation as eclipse
technology project.
What I don't understand is that if these projects are m
here is a workaround for 'incubation' within mature projects.
New optional experimental functionality may be shipped in examples plugins.
Regards
Ed Willink
On 16/12/2013 04:06, Igor Fedorenko wrote:
> Hello,
>
> I just pushed updated version of m2e 1.5 plan.
Hello,
I just pushed updated version of m2e 1.5 plan.xml to our git
repository [1]. I will let technology pmc and other eclipse powers
decide if this is good enough for m2e to stay in simultaneous release.
Also, in line with our "use latest released maven" recurring theme, we
updated m2e to incl
This was not about developers reviewing the changes. As I mentioned
upfront, I find gerrit very useful code review tool. I still believe
learning Gerrit is a berrier for prospect m2e contributors that are not
familiar with it. As long as m2e is not forced to accept contributions
through Gerrit, I
-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Igor
Fedorenko
Sent: October-04-13 1:54 PM
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Making your project more openŠhowto
enable Gerrit
Yes. Patches attached to
Yes. Patches attached to bugzilla are easier.
--
Regards,
Igor
On 2013-10-04 12:25 PM, Mickael Istria wrote:
On 10/04/2013 06:08 PM, Igor Fedorenko wrote:
m2e has no plans to accept gerrit contributions, at least not for now.
I'm curious: Why is this so? Did you find a process that
u think specifically will be confused by gerrit
enablement? The commiters? The contributors? Why? Do you think gerrit
itself is confusing?
On 04/10/2013 6:08 PM, Igor Fedorenko wrote:
m2e has no plans to accept gerrit contributions, at least not for now.
Having gerring enabled for m2e will be conf
m2e has no plans to accept gerrit contributions, at least not for now.
Having gerring enabled for m2e will be confusing.
--
Regards,
Igor
On 2013-10-04 10:22 AM, Doug Schaefer wrote:
I almost wonder if we should just enable Gerrit for all projects. That's
what we do internally here for all git
Speaking of b3 editor, am I the only one who can't change feature
categories in kepler aggregator? I've opened 414269 several weeks ago,
still waiting for any response.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=414269
--
Regards,
Igor
On 2013-09-13 12:27 PM, David M Williams wrote:
I fir
+43.662.457915.6
-Original Message-
From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Igor
Fedorenko
Sent: Thursday, September 05, 2013 2:15 AM
To: Cross project issues
Subject: [cross-project-issues-dev] proposal: active
, if not a few months.
Wayne
On 09/05/2013 12:54 PM, Igor Fedorenko wrote:
You didn't answer my question. When do you expect to have decision on
this new policy?
--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
<http://www.eclipse.org>
Learn about E
d and turn off a dozen checkboxes in the preferences?
The right answer _might_ be that we permit plug-ins to just send a
heartbeat without providing any ability to opt-out. My sense is that
this has potential to set off a tremendous backlash.
Or maybe I'm just being stupid and paranoid.
Wayne
ou expect
conclusive decision on 413169? Also, can you provide a link to the policy?
--
Regards,
Igor
Wayne
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=413169
On 09/05/2013 07:44 AM, Igor Fedorenko wrote:
On 2013-09-05 4:00 AM, Markus Alexander Kuppe wrote:
On 09/05/2013 02:14 AM
On 2013-09-05 4:00 AM, Markus Alexander Kuppe wrote:
On 09/05/2013 02:14 AM, Igor Fedorenko wrote:
* There will be workspace preference to enable the counting, it will be
on by default.
Does this mean that the plug-in collects statistics even if the user
does not opt-in to send stats?
No
e
to completely remove the plugin, if you want to be absolutely sure
installation count is never reported. (and you probably want to stop
using p2 because it always reports installation stats).
--
Regards,
Igor
Regards
Ed Willink
On 05/09/2013 01:14, Igor Fedorenko wrote:
As you
As you may or may not know, p2 can be configured to report feature or
plugin "download stats" to a remote server [1]. As a side note, this
reporting is done silently, i.e., without telling the user, and both
installations from remote servers and local filesystem are reported.
I would like to prop
@eclipse.org
<mailto:cross-project-issues-dev-boun...@eclipse.org>
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Igor
Fedorenko
Sent: Wednesday, August 21, 2013 1:26 PM
To: cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>
Subject: Re: [cr
consuming. After all, you don't want to just
pickup the random newest version. That's a lot more work.
- Konstantin
-Original Message-
From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Igor
Fedorenko
Sent: Wed
what yearly release.
--
Regards,
Igor
On 2013-08-21 3:47 PM, Matthias Sohn wrote:
On Wed, Aug 21, 2013 at 7:45 PM, Igor Fedorenko mailto:ifedore...@sonatype.com>> wrote:
Again, I am not arguing against building with individual dependency
repositories. All I am saying there is cur
a build
target, but it will make such strategy less fraught with problems.
- Konstantin
-Original Message-
From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Igor
Fedorenko
Sent: Wednesday, August 21, 2013 8:36 AM
To: c
#x27;t building against the bits that will
appear with your bits in this round's simrel repo. Doesn't that open up
the potential for bad things?
Doug.
On 13-08-21 7:29 AM, "Igor Fedorenko" wrote:
I did the same, too. I simply don't have the time needed to maintain
lis
I did the same, too. I simply don't have the time needed to maintain
list of project-level repositories and will build against kepler until I
can switch to luna simrel repo.
--
Regards,
Igor
On 2013-08-21 4:05 AM, Marcel Bruch wrote:
Maybe it would help if project could publish a (stable) URL o
On 2013-08-21 12:00 AM, David M Williams wrote:
Remember, enable your contribution if you plan to participate (remove
the "enabled="false"), but disable your repository if you are simply
waiting for pre-reqs to get enabled or fixed (disable by adding
enabled="false" to your repository element(s
nor upgrades, only service field upgrades.
Its a "balancing act" to allow projects to add new features to a service
release, yet still the kind of quality and stability users and adopters
expect from a service release.
I hope that gets at what you were asking. Let me know if I'm missi
the SR?
Sent from my BlackBerry 10 smartphone on the Rogers network.
*From: *Igor Fedorenko
*Sent: *Wednesday, August 14, 2013 11:24 AM
*To: *cross-project-issues-dev@eclipse.org
*Reply To: *Cross project issues
*Subject: *Re: [cross-project-issues-dev] Question on Kepler SR1 release
review
Can you elaborate? Using m2e as an example, what repositories am I
supposed to use to resolve jdt, xml editor and emf dependencies needed
to build m2e Luna M1?
--
Regards,
Igor
On 2013-08-14 7:33 PM, David M Williams wrote:
Nope. If you need that ... sounds like you are doing something wrong :)
Is "new releases must be released a month before SR RC1" a new requirement?
--
Regards,
Igor
On 2013-08-14 6:53 PM, David M Williams wrote:
I'll take this topic as a good segue to summarize Planning Council's
view on "more frequent releases" and "including new features in SRs".
I'll try to keep
I am not sure I understand the expected process for projects that have
their dependencies disabled in the aggregator. Are we supposed to check
from time to time to see when dependencies become enabled or there is a
way to tell b3 aggregator "enable contribution when all prereqs are
available"?
--
On 2013-07-30 5:52 PM, Mickael Istria wrote:
And seriously what again is "Standard" vs Java vs Java EE ?
I agree with that point. I'd rather see those 3 ones replaced with a
general "Java and JEE" package. It seems to make total sense with the
current status of Java development use-cases.
d. Committers have the right and in fact an obligation to
maintain design integrity; sometimes that annoys people.In any case,
we're not obligated to spend every waking moment of every day to fix
every reported problem, though it sometimes feels that way
Regards,
Ed
On 12/07/2013 7
How is this going to help? In most/all cases bugs are not fixed because
nobody comes forward with quality fixes. Weather somebody says "it needs
to be fixed" does not matter unless his/her words are backed up by the
code.
--
Regards,
Igor
On 2013-07-12 11:50 PM, Ed Willink wrote:
Hi
Get a comm
I don't think this is a workable approach.
First, such a test needs to run on all supported platform and jvm
combinations, which makes already involved task pretty much impossible
to perform, at least for small dev teams like we have in m2e.
Second, this won't actually find interoperability prob
ssues-dev-boun...@eclipse.org] on behalf of Igor Fedorenko
[ifedore...@sonatype.com]
Sent: Tuesday, July 02, 2013 3:49 PM
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] 6 month release cycle
I agree, one year is way too long. I am not even sure 6 months is often
e
I agree, one year is way too long. I am not even sure 6 months is often
enough. We had three m2e releases between Juno and Kepler, and I
consider m2e mature, (relatively) low-activity project. At the same
time, I never use R builds myself, I always use M-builds as primary
development environment f
See how we do this in m2e
https://git.eclipse.org/c/m2e/m2e-core.git/tree/pom.xml?id=releases/1.3/1.3.1.20130219-1424#n207
--
Regards,
Igor
On 2013-04-09 9:05 AM, Ahmed Wafa wrote:
Hello everyone,
I'm sorry if this was discussed somewhere. I wanted to ask how can I
sign jars generated from a
From the log it appears the build is trying to access Maven Central
repository directly but this connection times out for whatever reason.
Check if your firewall allows this connection or if you need to
configure http proxy, for example
http://maven.apache.org/settings.html#Proxies
--
Regards,
I
Is there special product/component or something else I need to set on
the bug to get webmaster's attention? The wiki says "open a bug that
blocks bug 324116". I did that for m2e few weeks ago, but nothing happened.
--
Regards,
Igor
On 12-10-10 12:46 PM, Henrik Rentz-Reichert wrote:
Hi Igor,
fo
it might be
nice for the webmasters to add the toolchains.xml file to the correct
location, I can raise a bugzilla for this if the answer to both
questions is "yes" (i.e. it will not impact any existing build) :).
Laurent
On 25/09/2012 15:00, Igor Fedorenko wrote:
You need to create tool
re that tycho can report the path "where"
it looked for the toolchains.xml file, but I don't know how to specify
this switch to the hudson build.
Laurent
[1]
https://hudson.eclipse.org/hudson/view/Modeling/job/emf-compare-master/326/console
[2] https://hudson.eclipse.org/hudson/view
toolchain.xml must be available on slave in ~/.m2 directory. You can
find sample toolchain.xml and libraries that correspond to restricted
execution environments attached to bug 386649 [1]. Beware that there is
currently an outstanding issue with IBM JDKs tracked as bug 389856 [2]
[1] https://bug
FYI, this does not currently produce usable pack200 files due to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=387557
--
Regards,
Igor
On Fri, Aug 17, 2012 at 10:32 PM, Igor Fedorenko
wrote:
> I "deployed" the new eclipse jarsigner plugin to [1]. This is not ideal,
> but I p
needed processing of m2e bundles and invalidates jar file
signature while doing that.
--
Regards,
Igor
On Sun, Aug 19, 2012 at 9:50 AM, Igor Fedorenko wrote:
> Agrregator build still fails so I disabled m2e contribution.
>
> --
> Regards,
> Igor
>
> On Sun, Aug 19, 2012 a
Agrregator build still fails so I disabled m2e contribution.
--
Regards,
Igor
On Sun, Aug 19, 2012 at 9:20 AM, Igor Fedorenko wrote:
> I rebuilt everything using java6 and published new 1.2.0.20120819-1116
> repo. I also removed all previous m2e 1.2 repos to avoid any possible
>
writing them with Java 6 as a
test? And/or, seems the general advise from bug 361628 is to set
jarprocessor.exclude.children=true
in your ellipse.inf file.
HTH
From: Igor Fedorenko
To: David M Williams/Raleigh/IBM@IBMUS, Cross project issues
,
Date: 08/18/2012 11:16 PM
Subject: Re: [cros
e wrong.
I just found it interesting that someone was using it. Good to know.
From: Igor Fedorenko
To: cross-project-issues-dev@eclipse.org,
Date: 08/19/2012 07:36 AM
Subject: Re: [cross-project-issues-dev] [keplerAggregation] Failed for
build 2012-08-18_16-50-43
Sent by: cross-project-issue
failing for all your jars, so, if it it is only on the
nested jars it is failing, you might try writing them with Java 6 as a
test? And/or, seems the general advise from bug 361628 is to set
jarprocessor.exclude.children=true
in your ellipse.inf file.
HTH
From: Igor Fedorenko
To: David M W
I will need some help with this. I verified that both jar and pack.gz
files in m2e repository are correctly signed and pass "jarsigner
-verify" test. I also verified that changing META-INF/eclipse.inf makes
"jarsigner -verify" test fail, so as far as I can tell everything is good.
What does "the
I just updated m2e contribution to Juno SR1 to version 1.2.0, up from
1.1.0 shipped in SR0. Nothing "on the train" depends on m2e as far as I
know, so I don't expect this change to cause any problem. But if you see
anything weird... you know who to blame ;-)
--
Regards,
Igor
_
On 12-08-15 9:49 AM, Matthias Sohn wrote:
let us know when this new signing plugin is available
--
Matthias
2012/8/15 Igor Fedorenko mailto:ifedore...@sonatype.com>>
Short term it maybe faster to deploy eclipse-signing-maven-plugin to one
of existing maven forgers, like oss.sonatype.
plugin is available
--
Matthias
2012/8/15 Igor Fedorenko mailto:ifedore...@sonatype.com>>
Short term it maybe faster to deploy eclipse-signing-maven-plugin to one
of existing maven forgers, like oss.sonatype.org
<http://oss.sonatype.org> we run, and use it from
there. At l
Short term it maybe faster to deploy eclipse-signing-maven-plugin to one
of existing maven forgers, like oss.sonatype.org we run, and use it from
there. At least this is what I plan to do for the new signing plugin I
wrote for cbi build.
--
Regards,
Igor
On 12-08-15 9:15 AM, Markus Tiede wrote:
I know I probably asked this last year... and the year before last
too... but how do I enable a project?
--
Regards,
Igor
On 12-08-14 5:08 PM, David M Williams wrote:
But, that still leaves 49 to go!
Remember, next week we will be producing Kepler M1 as well as Juno SR1
RC1 ... all Monday thro
Can we do this now or should we wait until next week?
--
Regards,
Igor
On 12-06-21 12:20 PM, Ian Skerrett wrote:
All,
We have added a new market on Marketplace called Eclipse Juno Projects.
This will make it a lot easier for people to find the Juno projects in
the the Marketplace Client.
When
I am sorry if this is a question with an obvious answer but who is
supposed reader audience for the release review documents and what
"they" expect to find in the docs?
--
Regards,
Igor
___
cross-project-issues-dev mailing list
cross-project-issues-dev@
No, I mean publish artifacts for real, with p2 metadata and everything
needed to reference them from b3 aggregator.
--
Regards,
Igor
On 12-06-13 7:33 AM, Dennis Hübner wrote:
Am 13.06.2012 um 12:49 schrieb Igor Fedorenko:
What harm in uploading last RC build to the final release location
What harm in uploading last RC build to the final release location
before 6/25 (or whatever the date is)?
--
Regards,
Igor
On 12-06-12 11:38 PM, David M Williams wrote:
It is important to make sure the b3aggrcon files point to something that
allows a "quick last minute rebuild" to be performed,
could discuss what to do about it, if
anything.
Thanks,
Inactive hide details for Igor Fedorenko ---05/26/2012 06:30:42 PM---I
believe these expired certificates cause P2 to download Igor Fedorenko
---05/26/2012 06:30:42 PM---I believe these expired certificates cause
P2 to download both pack.g
I believe these expired certificates cause P2 to download both pack.gz
and jar flavours of the same artifact when Eclipse is running on SUN
Java 7. At least this is the behaviour I see with Juno M7 P2 runtime
included with Tycho. Don't know if newer P2 behaves differently or if
the problem is limi
Tycho 0.13 and newer generate optional/non-greedy p2 requirements, which
I believe is the new behaviour.
--
Regards,
Igor
On 12-05-25 2:19 PM, Greg Watson wrote:
Martin,
Many thanks for this.
Sorry if this is a dumb question, but how do we know what publisher
we're using? We're using maven/t
ould I start investigating?
I'd investigate. I assume you are expect something later than 1.1.0?
Looks like your m2e.b3aggrcon file has not been updated since November
of last year? (When it was changed from 1.0.0, to 1.1.0).
Thanks,
Inactive hide details for Igor Fedorenko ---05/06/2012
Hello, David,
Staging repository [1] appears to contain older version of m2e. Is this
expected at this point or should I start investigating?
[1] http://download.eclipse.org/releases/staging/
--
Regards,
Igor
On 12-05-06 3:38 PM, David M Williams wrote:
Yes ... its here, M7 week! And, I'm alr
p2.Mirror support is unlikely to happen in Tychp. p2.Mirror is about
published repositories and Tycho build simply does not cover repository
publishing.
In theory, artifact signing can be implemented as part of Tycho, but
current Eclipse signing process makes this not possible in practice due
to
On 12-02-16 5:47 AM, Markus Knauer wrote:
Hi all,
This morning I found out that there is a status page at
https://dev.eclipse.org/committers/help/status.php available, but I
think this is not enough.
Was the status page available during the yesterday's outage?
--
Regards,
Igor
___
I see the same from Canada, too.
--
Regards,
Igor
On 12-02-08 5:10 AM, Laurent Goubet wrote:
Hi folks,
We have experienced recently (in the last 3-4 days) random "connection
was reset" errors when browsing the eclipse.org website (forum, project
pages, portal...). This affects both firefox and
I am not sure I understand what you recommend. Using m2e as an example.
Our goal is to maintain compatibility with at least one previous Eclipse
release. The version we ship with Juno is expected to install and wort
on Indigo. So we build m2e against Indigo and then test with both Indigo
and Juno.
1 - 100 of 114 matches
Mail list logo
