6:25 p.m.
Hey,
If we branched for JBT 4.1 Alpha next week would you be ok ?
Koen and Denis did an awesome job of at least getting Hibernate JPA/Dali integration
compiling this week.
And as Nick announced our simplest plan moving forward is to compile JBT 4.1 which will be
basis for JBDS 7 against Kepler (theoretically we could have something working
on both but it would be a massive QE effort).
Eclipse Kepler M5 is coming out Friday so we might still have some issues but Nick/Mistria
will be setting up a M5 based target platform as soon as possible.
It would be great if we could get out an early Alpha to get some traction and figure out
what issues we got to fight when it all comes together.
Could you let me know ASAP if you have any issues/concerns with doing a branch next week
for an Alpha build ? Would you be ready ?
Being ready for this means:
1) tested your component works on M5
2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise it)
3) issues marked with N&N so you can get them documented
4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0 (we
still have to do this "too high jump" in our current setup -hopefully can fix
before next big version)
5) Branched your component with jbosstools-4.1.Alpha1x
Please let me know if you are ready for that or have questions/concerns.
Thanks,
Max
9:32 p.m.
Projects now building on Kepler M4 which have compile or test failures
include:
Server: https://issues.jboss.org/browse/JBIDE-13459
JavaEE: https://issues.jboss.org/browse/JBIDE-13460
To watch for red balls from your project, please use these views:
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/
(internal)
http://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_Trunk/
(external)
Cheers,
On 01/31/2013 12:25 PM, Max Rydahl Andersen wrote:
Hey,
If we branched for JBT 4.1 Alpha next week would you be ok ?
Koen and Denis did an awesome job of at least getting Hibernate JPA/Dali integration
compiling this week.
And as Nick announced our simplest plan moving forward is to compile JBT 4.1 which will
be basis for JBDS 7 against Kepler (theoretically we could have something working
on both but it would be a massive QE effort).
Eclipse Kepler M5 is coming out Friday so we might still have some issues but
Nick/Mistria will be setting up a M5 based target platform as soon as possible.
It would be great if we could get out an early Alpha to get some traction and figure out
what issues we got to fight when it all comes together.
Could you let me know ASAP if you have any issues/concerns with doing a branch next week
for an Alpha build ? Would you be ready ?
Being ready for this means:
1) tested your component works on M5
2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise it)
3) issues marked with N&N so you can get them documented
4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0 (we
still have to do this "too high jump" in our current setup -hopefully can fix
before next big version)
5) Branched your component with jbosstools-4.1.Alpha1x
Please let me know if you are ready for that or have questions/concerns.
Thanks,
Max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
12:39 a.m.
There are 295 compile errors in Hibernate Tools when using
wtp4x-sdk-I-3.5.0-20130125110508 (the latest WTP build).
Snjeza
On 1/31/2013 6:25 PM, Max Rydahl Andersen wrote:
Hey,
If we branched for JBT 4.1 Alpha next week would you be ok ?
Koen and Denis did an awesome job of at least getting Hibernate JPA/Dali integration
compiling this week.
And as Nick announced our simplest plan moving forward is to compile JBT 4.1 which will
be basis for JBDS 7 against Kepler (theoretically we could have something working
on both but it would be a massive QE effort).
Eclipse Kepler M5 is coming out Friday so we might still have some issues but
Nick/Mistria will be setting up a M5 based target platform as soon as possible.
It would be great if we could get out an early Alpha to get some traction and figure out
what issues we got to fight when it all comes together.
Could you let me know ASAP if you have any issues/concerns with doing a branch next week
for an Alpha build ? Would you be ready ?
Being ready for this means:
1) tested your component works on M5
2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise it)
3) issues marked with N&N so you can get them documented
4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0 (we
still have to do this "too high jump" in our current setup -hopefully can fix
before next big version)
5) Branched your component with jbosstools-4.1.Alpha1x
Please let me know if you are ready for that or have questions/concerns.
Thanks,
Max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
6:46 a.m.
We are working to fix it and down to 184 errors for keplerm5
pushed what I have to
https://github.com/dgolovin/jbosstools-hibernate/tree/keplerm5
Denis
On 01/31/2013 03:39 PM, Snjezana Peco wrote:
There are 295 compile errors in Hibernate Tools when using
wtp4x-sdk-I-3.5.0-20130125110508 (the latest WTP build).
Snjeza
On 1/31/2013 6:25 PM, Max Rydahl Andersen wrote:
> Hey,
>
> If we branched for JBT 4.1 Alpha next week would you be ok ?
>
> Koen and Denis did an awesome job of at least getting Hibernate JPA/Dali integration
compiling this week.
>
> And as Nick announced our simplest plan moving forward is to compile JBT 4.1 which
will be basis for JBDS 7 against Kepler (theoretically we could have something working
> on both but it would be a massive QE effort).
>
> Eclipse Kepler M5 is coming out Friday so we might still have some issues but
Nick/Mistria will be setting up a M5 based target platform as soon as possible.
>
> It would be great if we could get out an early Alpha to get some traction and figure
out what issues we got to fight when it all comes together.
>
> Could you let me know ASAP if you have any issues/concerns with doing a branch next
week for an Alpha build ? Would you be ready ?
>
> Being ready for this means:
> 1) tested your component works on M5
> 2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise
it)
> 3) issues marked with N&N so you can get them documented
> 4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0
(we still have to do this "too high jump" in our current setup -hopefully can
fix before next big version)
> 5) Branched your component with jbosstools-4.1.Alpha1x
>
> Please let me know if you are ready for that or have questions/concerns.
>
> Thanks,
> Max
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
8:08 p.m.
New subject: ACTION REQUIRED: Fwd: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?
Seems noone spotted this email - could everyone who are part of the core builds report
back on the 5 items ?
"1) tested your component works on M5
2) no remaining jiras on 4.1.Alpha1 (triage your component! if
questions ping/raise it)
3) issues marked with N&N so you can get them documented
4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0 (we
still have to do this "too high jump" in our current setup -hopefully can fix
before next big version)
5) Branched your component with jbosstools-4.1.Alpha1x "
Please note the branch is jbosstools-4.1.Alpha1x (note the x)
/max
Begin forwarded message:
From: Max Rydahl Andersen <max.andersen(a)redhat.com>
Subject: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next
week?
Date: 31 Jan 2013 12:25:43 EST
To: jbosstools-dev jbosstools-dev <jbosstools-dev(a)lists.jboss.org>
Hey,
If we branched for JBT 4.1 Alpha next week would you be ok ?
Koen and Denis did an awesome job of at least getting Hibernate JPA/Dali integration
compiling this week.
And as Nick announced our simplest plan moving forward is to compile JBT 4.1 which will
be basis for JBDS 7 against Kepler (theoretically we could have something working
on both but it would be a massive QE effort).
Eclipse Kepler M5 is coming out Friday so we might still have some issues but
Nick/Mistria will be setting up a M5 based target platform as soon as possible.
It would be great if we could get out an early Alpha to get some traction and figure out
what issues we got to fight when it all comes together.
Could you let me know ASAP if you have any issues/concerns with doing a branch next week
for an Alpha build ? Would you be ready ?
Being ready for this means:
1) tested your component works on M5
2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise it)
3) issues marked with N&N so you can get them documented
4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0 (we
still have to do this "too high jump" in our current setup -hopefully can fix
before next big version)
5) Branched your component with jbosstools-4.1.Alpha1x
Please let me know if you are ready for that or have questions/concerns.
Thanks,
Max
9:12 p.m.
New subject: ACTION REQUIRED: Fwd: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?
On 02/08/2013 11:08 AM, Max Rydahl Andersen wrote:
"1) tested your component works on M5
Done.
2) no remaining jiras on 4.1.Alpha1 (triage your component! if
questions ping/raise it)
Done.
3) issues marked with N&N so you can get them documented
Done. (Still need to document them but the issues are marked with N&N)
4) Verified your component .y. version number have been bumped i.e.
3.2.1 -> 3.3.0 (we still have to do this "too high jump" in our current setup
-hopefully can fix before next big version)
Done.
5) Branched your component with jbosstools-4.1.Alpha1x "
Done.
All of this is for common, javaee, jst
9:43 p.m.
New subject: ACTION REQUIRED: Fwd: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?
Which target platform(s) is/are used on Jenkins to build the components ?
Thanks
Best regards,
/Xavier
On Feb 8, 2013, at 9:12 PM, Alexey Kazakov wrote:
On 02/08/2013 11:08 AM, Max Rydahl Andersen wrote:
> "1) tested your component works on M5
Done.
> 2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise
it)
Done.
> 3) issues marked with N&N so you can get them documented
Done. (Still need to document them but the issues are marked with N&N)
> 4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0
(we still have to do this "too high jump" in our current setup -hopefully can
fix before next big version)
Done.
> 5) Branched your component with jbosstools-4.1.Alpha1x "
Done.
All of this is for common, javaee, jst
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
10:54 p.m.
New subject: ACTION REQUIRED: Fwd: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?
Your build log will state which version of .target file is being fetched
from Nexus. That version will map 1:1 to a folder on download.jboss.org.
For example:
Downloading:
https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
Maps to this target platform:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3...
Should you need to build against a different target platform than the
versions stated in the parent pom, you can override with this:
mvn verify -DTARGET_PLATFORM_VERSION=4.21.4.Final-SNAPSHOT
Cheers,
Nick
On 02/08/2013 03:43 PM, Xavier Coulon wrote:
Which target platform(s) is/are used on Jenkins to build the
components ?
Thanks
Best regards,
/Xavier
On Feb 8, 2013, at 9:12 PM, Alexey Kazakov wrote:
>
> On 02/08/2013 11:08 AM, Max Rydahl Andersen wrote:
>> "1) tested your component works on M5
> Done.
>
>> 2) no remaining jiras on 4.1.Alpha1 (triage your component! if
>> questions ping/raise it)
> Done.
>> 3) issues marked with N&N so you can get them documented
> Done. (Still need to document them but the issues are marked with N&N)
>> 4) Verified your component .y. version number have been bumped i.e.
>> 3.2.1 -> 3.3.0 (we still have to do this "too high jump" in our
>> current setup -hopefully can fix before next big version)
> Done.
>> 5) Branched your component with jbosstools-4.1.Alpha1x "
> Done.
>
> All of this is for common, javaee, jst
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org <mailto:jbosstools-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
7:45 a.m.
New subject: ACTION REQUIRED: Fwd: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?
On 02/08/2013 10:54 PM, Nick Boldt wrote:
Your build log will state which version of .target file is being
fetched
from Nexus. That version will map 1:1 to a folder on download.jboss.org.
For example:
> Downloading:
https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
Maps to this target platform:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3...
Should you need to build against a different target platform than the
versions stated in the parent pom, you can override with this:
> mvn verify -DTARGET_PLATFORM_VERSION=4.21.4.Final-SNAPSHOT
By the way, we do
maintain a "maximum" and "minimum" profiles for you
which define the version of target-platfrom we support. Instead of using
the -DTARGET_PLATFORM_VERSION and choosing a version of the TP, you
should use "-Pmaximum" or "-Pminimum" which will set you the right
version of supported Target Platfroms for this build.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
6:06 p.m.
New subject: ACTION REQUIRED: Fwd: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?
Currently, because Kepler 4.3.0.Final is not yet released, I have set
both min and max to the same value in both the 4.1.0.Alpha1 (stable
branch) and 4.1.0.Alpha2 (master branch) parent poms:
<!-- In case no profile fits your requested TP version,
directly override this property -->
<TARGET_PLATFORM_VERSION>4.30.3.Alpha1-SNAPSHOT</TARGET_PLATFORM_VERSION>
<!-- default value for the "maximum" profile: TODO:
switch to M6 bits (4.30.3.Alpha1) -->
<TARGET_PLATFORM_VERSION-maximum>4.30.3.Alpha1-SNAPSHOT</TARGET_PLATFORM_VERSION-maximum>
Once 4.3.0.Final (Kepler R) is released in June, we will start to have a
valid "maximum" target platform as well, based on maintenance builds
that will eventually become Kepler SR1 or SR2.
Also, there is no "-Pminimum" profile, because that's the default
operation. The profile "-Pmaximum" is a convenience method to selects
the default maximum so you don't have to set it explicitly with
-DTARGET_PLATFORM_VERSION=4.some.future.release-SNAPSHOT
--
Note too that the latest Kepler target platform is now version
4.30.3.Alpha1-SNAPSHOT (not .2) because we had to update to use Eclipse
4.3M5a bits, newer BIRT, WTP, and the overall Kepler release.
N
On 02/11/2013 01:45 AM, Mickael Istria wrote:
On 02/08/2013 10:54 PM, Nick Boldt wrote:
> Your build log will state which version of .target file is being fetched
> from Nexus. That version will map 1:1 to a folder on download.jboss.org.
>
> For example:
>
> > Downloading:
>
https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too...
>
> Maps to this target platform:
>
>
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3...
>
> Should you need to build against a different target platform than the
> versions stated in the parent pom, you can override with this:
>
> > mvn verify -DTARGET_PLATFORM_VERSION=4.21.4.Final-SNAPSHOT
By the way, we do maintain a "maximum" and "minimum" profiles for
you
which define the version of target-platfrom we support. Instead of using
the -DTARGET_PLATFORM_VERSION and choosing a version of the TP, you
should use "-Pmaximum" or "-Pminimum" which will set you the right
version of supported Target Platfroms for this build.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
11:11 p.m.
New subject: ACTION REQUIRED: Fwd: JBoss Tools 4.1 Alpha based on Kepler - ready for branch for build ETA next week?
Thanks Alexey!
/max
On 08 Feb 2013, at 15:12, Alexey Kazakov <akazakov(a)exadel.com> wrote:
On 02/08/2013 11:08 AM, Max Rydahl Andersen wrote:
> "1) tested your component works on M5
Done.
> 2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions ping/raise
it)
Done.
> 3) issues marked with N&N so you can get them documented
Done. (Still need to document them but the issues are marked with N&N)
> 4) Verified your component .y. version number have been bumped i.e. 3.2.1 -> 3.3.0
(we still have to do this "too high jump" in our current setup -hopefully can
fix before next big version)
Done.
> 5) Branched your component with jbosstools-4.1.Alpha1x "
Done.
All of this is for common, javaee, jst
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
8:55 p.m.
1) tested your component works on M5
in the doing
2) no remaining jiras on 4.1.Alpha1 (triage your component! if
questions ping/raise it)
done
3) issues marked with N&N so you can get them documented
in the doing
4) Verified your component .y. version number have been bumped i.e.
3.2.1 -> 3.3.0 (we still have to do this "too high jump" in our current setup
-hopefully can fix before next big version)
done, bumped 2.4.0 -> 2.5.0
5) Branched your component with jbosstools-4.1.Alpha1x
done
9:18 p.m.
On 02/08/2013 09:13 PM, Denis Golovin wrote:
Branch name should be jbosstools-4.1*.0*.Alpha1
you mean
jbosstools-4.1.0.Alpha1x
right?
On 02/08/2013 11:55 AM, André Dietisheim wrote:
>> 1) tested your component works on M5
> in the doing
>
>> 2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions
ping/raise it)
> done
>
>> 3) issues marked with N&N so you can get them documented
> in the doing
>
>> 4) Verified your component .y. version number have been bumped i.e. 3.2.1 ->
3.3.0 (we still have to do this "too high jump" in our current setup -hopefully
can fix before next big version)
> done, bumped 2.4.0 -> 2.5.0
>
>> 5) Branched your component with jbosstools-4.1.Alpha1x
> done
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
10:49 p.m.
Branch name should be jbosstools-4.1.0.Alpha1
+1. Note the 0 and lack of superfluous 'x'.
Nick
On 02/08/2013 03:13 PM, Denis Golovin wrote:
Branch name should be jbosstools-4.1*.0*.Alpha1
On 02/08/2013 11:55 AM, André Dietisheim wrote:
>> 1) tested your component works on M5
> in the doing
>
>> 2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions
ping/raise it)
> done
>
>> 3) issues marked with N&N so you can get them documented
> in the doing
>
>> 4) Verified your component .y. version number have been bumped i.e. 3.2.1 ->
3.3.0 (we still have to do this "too high jump" in our current setup -hopefully
can fix before next big version)
> done, bumped 2.4.0 -> 2.5.0
>
>> 5) Branched your component with jbosstools-4.1.Alpha1x
> done
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
11:55 p.m.
Gawd - sorry for that confusion.
jbosstools-4.1.0.Alpha1x :)
Just for those wondering about why the "x" is there is because git doesn't
allow track and branches have the same name like svn did/does.
/max
On 08 Feb 2013, at 16:49, Nick Boldt <nboldt(a)redhat.com> wrote:
> Branch name should be jbosstools-4.1.0.Alpha1
+1. Note the 0 and lack of superfluous 'x'.
Nick
On 02/08/2013 03:13 PM, Denis Golovin wrote:
> Branch name should be jbosstools-4.1*.0*.Alpha1
>
> On 02/08/2013 11:55 AM, André Dietisheim wrote:
>>> 1) tested your component works on M5
>> in the doing
>>
>>> 2) no remaining jiras on 4.1.Alpha1 (triage your component! if questions
ping/raise it)
>> done
>>
>>> 3) issues marked with N&N so you can get them documented
>> in the doing
>>
>>> 4) Verified your component .y. version number have been bumped i.e. 3.2.1
-> 3.3.0 (we still have to do this "too high jump" in our current setup
-hopefully can fix before next big version)
>> done, bumped 2.4.0 -> 2.5.0
>>
>>> 5) Branched your component with jbosstools-4.1.Alpha1x
>> done
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
4372
days inactive
4383
days old
jbosstools-dev@lists.jboss.org
17 comments
8 participants
participants (8)
-
Alexey Kazakov -
André Dietisheim -
Denis Golovin -
Max Rydahl Andersen -
Mickael Istria -
Nick Boldt -
Snjezana Peco -
Xavier Coulon