have now control over the version to be used
> and we’ll stick to it.
>
> BR,
> Bernd
>
>
> *From:* cross-project-issues-dev-boun...@eclipse.org <
> cross-project-issues-dev-boun...@eclipse.org> *On Behalf Of *Ed Willink
> *Sent:* February-17-19 6:52 AM
> *To:* cross-pr
clipse.org
> <mailto:cross-project-issues-dev-boun...@eclipse.org>
> <mailto:cross-project-issues-dev-boun...@eclipse.org>> On Behalf Of Ed Willink
> Sent: February-17-19 6:52 AM
> To: cross-project-issues-dev@eclipse.org
> <mailto:cross-project-issues-dev@eclipse.org>
to be used and
we’ll stick to it.
BR,
Bernd
From: cross-project-issues-dev-boun...@eclipse.org
On Behalf Of Ed Willink
Sent: February-17-19 6:52 AM
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
Hi
Yes
Hi
Yes. Correction. Time flies. It was Java 8 that chnaged the implementation.
You are certainly right that build.properties did not allow 1.0.0 and
2.0.0 annotations to co-exist, pretty much mandating a migration.
But I am really surprised that you can have *.class files referencing
o.e.jdt.annotation 2.0.0 exploits Java 7 type annotations which
persist at run-time. You must therefore require o.e.jdt.annotation
just like any other bundle.
You meant Java 8. And they are not available at runtime (they use
RetentionPolicy.CLASS), therefore the bundle.properties mechanism
rom: cross-project-issues-dev-boun...@eclipse.org
On Behalf Of Carsten Reckord
Sent: February-15-19 5:09 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
Hi Bernd,
I still try to understand why the change in my target definit
19 5:09 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
Hi Bernd,
> I still try to understand why the change in my target definition to
> use a different platform updates site causes this particular failure
> while
Hi Bernd,
> I still try to understand why the change in my target definition to use a
> different platform updates site causes this particular failure while using the
> same java, tycho and Trace Compass version. I don't see the connection.
You could use mvn -X -Dtycho.debug.resolver=true to
4-19 11:34 AM
*To:* Cross project issues
*Subject:* Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
I can't say much without more details. The error looks strange. It's
not directly a Java compile error but an issue with visibility/access
based on the class path. What
rom: cross-project-issues-dev-boun...@eclipse.org
On Behalf Of Daniel Megert
Sent: February-14-19 11:34 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
I can't say much without more details. The error looks strange. It's not
:Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
Sent by:cross-project-issues-dev-boun...@eclipse.org
Hi Dani
The only change is the platform version. The patch on Gerrit had other
things. But I can reproduce it on my laptop where I only change
-project-issues-dev-boun...@eclipse.org
On Behalf Of Daniel Megert
Sent: February-14-19 11:07 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
Did you check whether something change, e.g. JRE or Tycho version?
Dani
From
Did you check whether something change, e.g. JRE or Tycho version?
Dani
From: Bernd Hufmann
To: Cross project issues
Date: 14.02.2019 17:01
Subject:Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
Sent by:cross-project-issues-dev-boun
form or other)?
Bernd
From: cross-project-issues-dev-boun...@eclipse.org
On Behalf Of Vikas Chandra
Sent: February-14-19 12:51 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Build problems with recent
platform4.11-I-builds
>>is there something that I could do i
Hi,
For the Trace Compass project, I changed the target definition to use the
latest platform integration build and I get some unexpected compilation errors
when building with tycho. Reference [1] shows a Jenkins build for the failure.
See below for an example of the error print-outs. See
I've been trying to start a build for Scout 3.9 for the RC3 release today.
Unfortunately, Hudson seems to be very slow and to stuck at the build [1].
Does anyone have the same problem?
[1] https://hudson.eclipse.org/hudson/job/cbi-scout-3.9-nightly/459/console
smime.p7s
Description: S/MIME
@eclipse.org
Subject: [cross-project-issues-dev] Build problems on Hudson
I've been trying to start a build for Scout 3.9 for the RC3 release today.
Unfortunately, Hudson seems to be very slow and to stuck at the build [1].
Does anyone have the same problem?
[1] https://hudson.eclipse.org/hudson/job
If your console log is very large, rendering it can actually slow the
master down considerably.
Also, there are currently 12 threads trying to fetch:
GET
/hudson/me/my-views/view/Graphiti/job/gmp-graphiti-nightly/ws/last_success/site.packed/*zip*/site.packed.zip
That is not good :(
I'll
I don't see that problem exactly, but do see the permissions for
signing, for both eclipse and orbit seem messed up.
From: Greg Watson g.wat...@computer.org
To: Cross project issues cross-project-issues-dev@eclipse.org,
Date: 04/18/2013 10:42 PM
Subject:[cross-project-issues
Am 19.04.2013 04:42, schrieb Greg Watson:
We're seeing this error on hudson. Is anyone else having problems?
We also have permission issues with our build. It seems that the ACLs
permissions on /shared are all lost (in our case).
-Gunnar
--
Gunnar Wagenknecht
gun...@wagenknecht.org
I'm working to restore the ACLs.
-Matt.
We also have permission issues with our build. It seems that the ACLs
permissions on /shared are all lost (in our case).
-Gunnar
___
cross-project-issues-dev mailing list
We're seeing this error on hudson. Is anyone else having problems?
Thanks,
Greg
[INFO] Building zip:
https://hudson.eclipse.org/hudson/job/ptp-master-nightly/ws/target/packed/org.eclipse.ptp.master-7.0.0-SNAPSHOT.zip-after-removing.zip
[ERROR]
org.apache.maven.plugin.MojoFailureException:
22 matches
Mail list logo
