From nboldt at redhat.com  Sun Mar  1 19:18:21 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Sun, 01 Mar 2015 19:18:21 -0500
Subject: [jbosstools-dev] JBoss Tools Core 4.2.3.Beta1 bits available for
	community & QE testing
Message-ID: <54F3AC4D.60709@redhat.com>

As always, these are not FINAL bits, but preliminary results for 
community & QE testing. Not for use by customers or end users.

Update site: http://download.jboss.org/jbosstools/updates/staging/luna/

Target platforms:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Final 

* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.42.0.Beta1-SNAPSHOT 


Until the above target platform site is released, you may need to add it 
to Eclipse to resolve dependencies at install time.
Once released, dependencies will be found automatically from here:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ 
(latest release)
* 
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.42.0.Beta1-SNAPSHOT/ 
(upcoming milestone)
* 
http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.42.0.Beta1-SNAPSHOT/ 
(upcoming milestone)

New + noteworthy (subject to change):
* 
https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
* http://tools.jboss.org/documentation/whatsnew/

Schedule: 
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel

--

Additional update sites:
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.Beta1-updatesite-core/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.Beta1-updatesite-coretests/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.Beta1-updatesite-hibernatetools/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.Beta1-updatesite-webtools/
and build sites:
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Beta1-build-core/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Beta1-build-coretests/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Beta1-build-hibernatetools/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Beta1-build-webtools/


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From xcoulon at redhat.com  Mon Mar  2 05:38:28 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Mon, 2 Mar 2015 11:38:28 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
	please tag your projects [ branch jbosstools-4.3.0.Alpha1x -> tag
	jbosstools-4.3.0.Alpha1 ]
In-Reply-To: <54E7B85E.2040108@gmail.com>
References: <54E7B85E.2040108@gmail.com>
Message-ID: <F9973DC8-EF70-4E88-8933-C32FE0974291@redhat.com>

Done for Webservices and Livereload.
Sorry for the delay.

Best regards,
/Xavier



> On 20 Feb 2015, at 23:42, Nick Boldt <nickboldt at gmail.com> wrote:
> 
> Component leads, please tag your repositories!
> 
> $ git fetch jbosstools jbosstools-4.3.0.Alpha1x #assuming remote is 
> called jbosstools, also often called origin
> $ git tag jbosstools-4.3.0.Alpha1 FETCH_HEAD
> $ git push jbosstools jbosstools-4.3.0.Alpha1
> 
> 
> -- 
> Nick Boldt :: http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150302/8b019e7c/attachment.html 

From nboldt at redhat.com  Tue Mar  3 11:47:56 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 03 Mar 2015 11:47:56 -0500
Subject: [jbosstools-dev] FYI: Some old target platforms have been removed
Message-ID: <54F5E5BC.9080308@redhat.com>

Recently, as part of the annual maintenance / cleanup we do on the 
servers, I removed some old target platforms which should no longer be 
needed by downstream projects.

Should this change impact you, you have two options:

a) let me know and I can revert the change

b) rebuild your project using the newer target platform

Affected projects - if any - are likely those in the Integration Stack 
who haven't updated their builds to use the latest Juno SR2 or Kepler 
SR2 target platforms (still using SR1, for example).

Ref: https://issues.jboss.org/browse/JBIDE-18914

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From manderse at redhat.com  Wed Mar  4 06:49:13 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Wed, 4 Mar 2015 06:49:13 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201503041149.t24BnDOT010348@int-mx14.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-19396

https://issues.jboss.org/browse/JBIDE-19396
Summary: Add JAX-RS facet for JAX-RS resource

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 5:57:46.835235

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From fbricon at redhat.com  Wed Mar  4 09:14:16 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Wed, 4 Mar 2015 09:14:16 -0500
Subject: [jbosstools-dev] [Bug 1178800] Warnings when importing
	hibernate3 quickstart into JBDS
In-Reply-To: <bug-1178800-316614-PNgfuhvBm3@bugzilla.redhat.com>
References: <bug-1178800-316614@bugzilla.redhat.com>
	<bug-1178800-316614-PNgfuhvBm3@bugzilla.redhat.com>
Message-ID: <FCE4EE10-FB57-4DD0-BB79-0C93418C607C@redhat.com>

Koen, Alexey, any idea?

> Le 4 mars 2015 ? 07:35, bugzilla at redhat.com a ?crit :
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1178800
> 
> sgilda at redhat.com changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Flags|                            |needinfo?(fbricon at redhat.co
>                   |                            |m)
> 
> 
> 
> --- Comment #9 from sgilda at redhat.com ---
> Now I can recreate the following JSF Faces Config Problems:
> 
> validator-class references to
> "org.jboss.as.quickstart.hibernate3.util.ValidateEmail" that does not extend
> javax.faces.validator.Validator    faces-config.xml
> 
> validator-class references to
> "org.jboss.as.quickstart.hibernate3.util.ValidateMemberId" that does not extend
> javax.faces.validator.Validator    faces-config.xml
> 
> validator-class references to
> "org.jboss.as.quickstart.hibernate3.util.ValidateName" that does not extend
> javax.faces.validator.Validator    faces-config.xml
> 
> 
> But I do not see the JPA Problem: 
> 
> Console configuration "jboss-hibernate3" does not exist. Hibernate specific
> validation and content assist will be limited
> 
> @fbricon: Do you know what would cause the above issue?
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.
> Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=CzyjyGAehs&a=cc_unsubscribe



From nboldt at redhat.com  Wed Mar  4 11:36:21 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 04 Mar 2015 11:36:21 -0500
Subject: [jbosstools-dev] Upcoming release of Locus 1.2
Message-ID: <54F73485.208@redhat.com>

FYI, we're looking at doing a Locus 1.2 release sometime before JBoss 
Tools 4.3.Alpha2 is released.

Schedule and contents TBD.

There are currently 4 JIRAs under consideration:

* JBIDE-18721 New version of Saxon-HE required in locus [affects Teiid 
Designer]

* JBIDE-18108 Set version on exported packages (affects inclusion of 
Powermock?)

* JBIDE-18053 Add Powermock

* JBIDE-19392 Add jboss-dmr

---

For reference, the draft schedule for JBT 4.3 is here:

https://issues.jboss.org/browse/JBIDE?selectedTab=com.atlassian.jira.jira-projects-plugin%3Aversions-panel

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From akazakov at exadel.com  Wed Mar  4 14:35:45 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Wed, 04 Mar 2015 11:35:45 -0800
Subject: [jbosstools-dev] [Bug 1178800] Warnings when importing
 hibernate3 quickstart into JBDS
In-Reply-To: <FCE4EE10-FB57-4DD0-BB79-0C93418C607C@redhat.com>
References: <bug-1178800-316614@bugzilla.redhat.com>	<bug-1178800-316614-PNgfuhvBm3@bugzilla.redhat.com>
	<FCE4EE10-FB57-4DD0-BB79-0C93418C607C@redhat.com>
Message-ID: <54F75E91.80507@exadel.com>

These JSF Faces Config Problems is a bug in our JSF Tools. We will 
create an issue in JIRA to fix it.

On 03/04/2015 06:14 AM, Fred Bricon wrote:
> Koen, Alexey, any idea?
>
>> Le 4 mars 2015 ? 07:35, bugzilla at redhat.com a ?crit :
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1178800
>>
>> sgilda at redhat.com changed:
>>
>>            What    |Removed                     |Added
>> ----------------------------------------------------------------------------
>>               Flags|                            |needinfo?(fbricon at redhat.co
>>                    |                            |m)
>>
>>
>>
>> --- Comment #9 from sgilda at redhat.com ---
>> Now I can recreate the following JSF Faces Config Problems:
>>
>> validator-class references to
>> "org.jboss.as.quickstart.hibernate3.util.ValidateEmail" that does not extend
>> javax.faces.validator.Validator    faces-config.xml
>>
>> validator-class references to
>> "org.jboss.as.quickstart.hibernate3.util.ValidateMemberId" that does not extend
>> javax.faces.validator.Validator    faces-config.xml
>>
>> validator-class references to
>> "org.jboss.as.quickstart.hibernate3.util.ValidateName" that does not extend
>> javax.faces.validator.Validator    faces-config.xml
>>
>>
>> But I do not see the JPA Problem:
>>
>> Console configuration "jboss-hibernate3" does not exist. Hibernate specific
>> validation and content assist will be limited
>>
>> @fbricon: Do you know what would cause the above issue?
>>
>> -- 
>> You are receiving this mail because:
>> You are on the CC list for the bug.
>> Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=CzyjyGAehs&a=cc_unsubscribe
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From nboldt at redhat.com  Wed Mar  4 15:11:10 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 04 Mar 2015 15:11:10 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Beta1 ]
Message-ID: <54F766DE.70806@redhat.com>

Component leads, please tag your repositories!

$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
jbosstools, also often called origin
$ git tag jbosstools-4.2.3.Beta1 FETCH_HEAD
$ git push jbosstools jbosstools-4.2.3.Beta1


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From akazakov at exadel.com  Wed Mar  4 15:36:00 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Wed, 04 Mar 2015 12:36:00 -0800
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Beta1 ]
In-Reply-To: <54F766DE.70806@redhat.com>
References: <54F766DE.70806@redhat.com>
Message-ID: <54F76CB0.7040002@exadel.com>

Done for base, jst, javaee, hibernate, arquillian.

On 03/04/2015 12:11 PM, Nick Boldt wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.Beta1 FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.Beta1
>
>


From ggastald at redhat.com  Wed Mar  4 16:27:06 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Wed, 04 Mar 2015 18:27:06 -0300
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Beta1 ]
In-Reply-To: <54F766DE.70806@redhat.com>
References: <54F766DE.70806@redhat.com>
Message-ID: <54F778AA.4010600@redhat.com>

Done for forge.
Thanks!

On 03/04/2015 05:11 PM, Nick Boldt wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.Beta1 FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.Beta1
>
>


From fbricon at redhat.com  Wed Mar  4 17:15:51 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Wed, 4 Mar 2015 17:15:51 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
	please tag your projects [ branch jbosstools-4.2.x -> tag
	jbosstools-4.2.3.Beta1 ]
In-Reply-To: <54F766DE.70806@redhat.com>
References: <54F766DE.70806@redhat.com>
Message-ID: <A7B02428-6988-4842-946F-6000BEC1A782@redhat.com>

central done 

> Le 4 mars 2015 ? 15:11, Nick Boldt <nboldt at redhat.com> a ?crit :
> 
> jbosstools-4.2.3.Beta1

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150304/3ab5ef2c/attachment.html 

From adietish at redhat.com  Thu Mar  5 08:16:25 2015
From: adietish at redhat.com (=?windows-1252?Q?Andr=E9_Dietisheim?=)
Date: Thu, 05 Mar 2015 14:16:25 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Beta1 ]
In-Reply-To: <54F766DE.70806@redhat.com>
References: <54F766DE.70806@redhat.com>
Message-ID: <54F85729.9030800@redhat.com>

done for openshift.

On 03/04/2015 09:11 PM, Nick Boldt wrote:
> Component leads, please tag your repositories!
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.Beta1 FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.Beta1
>
>


From bfitzpat at redhat.com  Thu Mar  5 08:42:58 2015
From: bfitzpat at redhat.com (Brian Fitzpatrick)
Date: Thu, 5 Mar 2015 08:42:58 -0500 (EST)
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.Beta1 ]
In-Reply-To: <54F766DE.70806@redhat.com>
References: <54F766DE.70806@redhat.com>
Message-ID: <736128958.24056269.1425562978289.JavaMail.zimbra@redhat.com>

done for webservices

_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, Tooling
JBoss by Red Hat

----- Original Message -----
From: "Nick Boldt" <nboldt at redhat.com>
To: jbosstools-dev at lists.jboss.org
Sent: Wednesday, March 4, 2015 1:11:10 PM
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.3.Beta1 ]

Component leads, please tag your repositories!

$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
jbosstools, also often called origin
$ git tag jbosstools-4.2.3.Beta1 FETCH_HEAD
$ git push jbosstools jbosstools-4.2.3.Beta1


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev

From xcoulon at redhat.com  Thu Mar  5 09:33:26 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Thu, 5 Mar 2015 15:33:26 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
	please tag your projects [ branch jbosstools-4.2.x -> tag
	jbosstools-4.2.3.Beta1 ]
In-Reply-To: <54F766DE.70806@redhat.com>
References: <54F766DE.70806@redhat.com>
Message-ID: <4A7552E7-756B-4DCB-9330-933F69BC5976@redhat.com>

Done for LiveReload.

Best regards,
/Xavier



> On 04 Mar 2015, at 21:11, Nick Boldt <nboldt at redhat.com> wrote:
> 
> jbosstools-4.2.3.Beta1

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150305/c53a93fb/attachment-0001.html 

From nboldt at redhat.com  Thu Mar  5 14:49:36 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 05 Mar 2015 14:49:36 -0500
Subject: [jbosstools-dev] ACTION REQUIRED: Preparing for 4.2.3.CR1 CF next
	week [Mar 12]
Message-ID: <54F8B350.2050901@redhat.com>

Some steps need to be done to get ready for code freeze next week (March 
12).

These are:

a) rename/rebuild parent pom, upversioned to 4.2.3.CR1 [done]
b) rename/rebuild target platform
c) update projects *which will have changes for CR1* to use this latest 
parent pom

Rather than asking *everyone* to update their root pom and wasting your 
time w/ Task JIRAs, I'd rather ask this:

* Which projects plan to contribute changes to 4.2.3.CR1?

If you have changes, please upversion your parent pom to use 
4.2.3.CR1-SNAPSHOT.

If you do not, you need do nothing at this time.

If you would still like a Task JIRA next week, I can certainly create 
them. Just let me know which project(s) need them and I'll skip sending 
them to those who don't need them.


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From ggastald at redhat.com  Thu Mar  5 15:09:37 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 5 Mar 2015 15:09:37 -0500 (EST)
Subject: [jbosstools-dev] ACTION REQUIRED: Preparing for 4.2.3.CR1 CF
	next	week [Mar 12]
In-Reply-To: <54F8B350.2050901@redhat.com>
References: <54F8B350.2050901@redhat.com>
Message-ID: <3186BD26-4D3C-4084-A182-DA54E21B0A4D@redhat.com>

Updated in jbosstools-forge (jbosstools-4.2.x branch)



> Em 05/03/2015, ?s 16:49, Nick Boldt <nboldt at redhat.com> escreveu:
> 
> Some steps need to be done to get ready for code freeze next week (March 
> 12).
> 
> These are:
> 
> a) rename/rebuild parent pom, upversioned to 4.2.3.CR1 [done]
> b) rename/rebuild target platform
> c) update projects *which will have changes for CR1* to use this latest 
> parent pom
> 
> Rather than asking *everyone* to update their root pom and wasting your 
> time w/ Task JIRAs, I'd rather ask this:
> 
> * Which projects plan to contribute changes to 4.2.3.CR1?
> 
> If you have changes, please upversion your parent pom to use 
> 4.2.3.CR1-SNAPSHOT.
> 
> If you do not, you need do nothing at this time.
> 
> If you would still like a Task JIRA next week, I can certainly create 
> them. Just let me know which project(s) need them and I'll skip sending 
> them to those who don't need them.
> 
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From akazakov at exadel.com  Thu Mar  5 17:26:57 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 05 Mar 2015 14:26:57 -0800
Subject: [jbosstools-dev] JBoss Tools 4.2.3.Beta1 is now available
Message-ID: <54F8D831.2090606@exadel.com>


This is a development release aimed at Eclipse 4.4.2 Luna SR2 users.

Eclipse Marketplace: (will not posted to Marketplace until Final released)

Update Site: http://download.jboss.org/jbosstools/updates/development/luna/

Update Site Zips: 
http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.2.3.x/

Installation instructions: 
http://tools.jboss.org/downloads/installation.html

New + Noteworthy (subject to change): 
http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.3.Beta1.html

Schedule / Upcoming Releases: 
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel

Alexey Kazakov.

From akazakov at exadel.com  Thu Mar  5 17:27:03 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 05 Mar 2015 14:27:03 -0800
Subject: [jbosstools-dev] JBoss Developer Studio 8.1.0.Beta1 is available
Message-ID: <54F8D837.30300@exadel.com>

JBoss Developer Studio 8.1.0 is available!

Download page and installer:
* http://tools.jboss.org/downloads/devstudio/luna/8.1.0.Beta1.html
* https://www.jboss.org/products/devstudio/overview/

Update site: https://devstudio.redhat.com/updates/8.0-development/

Early Access site: https://devstudio.jboss.com/earlyaccess/8.0-development/

--

Eclipse Marketplace: (will not posted to Marketplace until Final released)

--

Schedule / Upcoming Releases: 
https://issues.jboss.org/browse/JBDS#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel

Alexey Kazakov.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150305/55905174/attachment.html 

From akazakov at exadel.com  Thu Mar  5 20:41:08 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 05 Mar 2015 17:41:08 -0800
Subject: [jbosstools-dev] ACTION REQUIRED: Preparing for 4.2.3.CR1 CF
 next week [Mar 12]
In-Reply-To: <54F8B350.2050901@redhat.com>
References: <54F8B350.2050901@redhat.com>
Message-ID: <54F905B4.1070803@exadel.com>

I updated the parent pom for base and server. We will probably change 
javaee and hibernate too. We will update the parent pom for them when 
merging those changes.

On 03/05/2015 11:49 AM, Nick Boldt wrote:
> Some steps need to be done to get ready for code freeze next week (March
> 12).
>
> These are:
>
> a) rename/rebuild parent pom, upversioned to 4.2.3.CR1 [done]
> b) rename/rebuild target platform
> c) update projects *which will have changes for CR1* to use this latest
> parent pom
>
> Rather than asking *everyone* to update their root pom and wasting your
> time w/ Task JIRAs, I'd rather ask this:
>
> * Which projects plan to contribute changes to 4.2.3.CR1?
>
> If you have changes, please upversion your parent pom to use
> 4.2.3.CR1-SNAPSHOT.
>
> If you do not, you need do nothing at this time.
>
> If you would still like a Task JIRA next week, I can certainly create
> them. Just let me know which project(s) need them and I'll skip sending
> them to those who don't need them.
>
>


From sal7 at qwrer.cctcra.com  Thu Mar  5 21:49:02 2015
From: sal7 at qwrer.cctcra.com (Remotely management advertising player / Attn: Technical Manager)
Date: Fri, 06 Mar 2015 02:49:02 +0000
Subject: [jbosstools-dev] =?gb2312?b?UmVtb3RlbHkgbWFuYWdlbWVudCBhZHZlcnRp?=
	=?gb2312?b?c2luZyBwbGF5ZXIgLyBBdHRuOiBUZWNobmljYWwgTWFuYWdlctPr?=
	=?gb2312?b?xPq5ss/twcvP4LLhoaM=?=
Message-ID: <90e6ba61459c233b59051095ba29@google.com>

Dear Sirs,

  After visiting your web-site I decided to contact your esteemed company as  
one of the leaders of digital signage field .

  MSP5000 is a multi monitor video wall processor, supporting to up  32  
channel display monitor. What is more MSP5000 can compatible with multi  
capture type, including IP camera ,DVI,VGA SDI and BNC .The PC and FPGA  
architecture offer users with stable, flexible and cost effective image  
processing capabilities.  All these features make it a good choice for  
surveillance application .

  I would appreciate if you forward this letter to Technical Manager or to  
other expert responsible for technical integration of new products in your  
company, or provide me with his contact for we could discuss all the  
details of our future cooperation.

Your early reply is highly appreciated

Anna

https://picasaweb.google.com/lh/sredir?uname=117610716181172159237&target=ALBUM&id=6116290175618037697&authkey=Gv1sRgCJioxu_lpariVA&invite=CK71yY0F&feat=email
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150306/fef92bce/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: picasaweblogo-zh_CN.gif
Type: image/gif
Size: 1646 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150306/fef92bce/attachment-0001.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: email.jpg
Type: image/jpeg
Size: 6905 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150306/fef92bce/attachment-0001.jpg 

From xcoulon at redhat.com  Fri Mar  6 12:51:26 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Fri, 6 Mar 2015 18:51:26 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: Preparing for 4.2.3.CR1 CF
	next week [Mar 12]
In-Reply-To: <54F8B350.2050901@redhat.com>
References: <54F8B350.2050901@redhat.com>
Message-ID: <0F69CAD6-2ABC-471F-9943-487BC2C76F21@redhat.com>

Updated in Web Services

Best regards,
/Xavier



> On 05 Mar 2015, at 20:49, Nick Boldt <nboldt at redhat.com> wrote:
> 
> Some steps need to be done to get ready for code freeze next week (March 
> 12).
> 
> These are:
> 
> a) rename/rebuild parent pom, upversioned to 4.2.3.CR1 [done]
> b) rename/rebuild target platform
> c) update projects *which will have changes for CR1* to use this latest 
> parent pom
> 
> Rather than asking *everyone* to update their root pom and wasting your 
> time w/ Task JIRAs, I'd rather ask this:
> 
> * Which projects plan to contribute changes to 4.2.3.CR1?
> 
> If you have changes, please upversion your parent pom to use 
> 4.2.3.CR1-SNAPSHOT.
> 
> If you do not, you need do nothing at this time.
> 
> If you would still like a Task JIRA next week, I can certainly create 
> them. Just let me know which project(s) need them and I'll skip sending 
> them to those who don't need them.
> 
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150306/acd04cf6/attachment.html 

From manderse at redhat.com  Sat Mar  7 06:15:47 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Sat, 07 Mar 2015 12:15:47 +0100
Subject: [jbosstools-dev] Locus jira being created
Message-ID: <E4C31D91-7AC3-4057-B11B-A5ADC623F6B1@redhat.com>

Hey,

Since Locus has its own release cycle i'm in progress of moving old 
locus component issues the https://jira.jboss.org/browse/LOCUS project.

Sorry for the notification noise - should be over shortly.


/max
http://about.me/maxandersen

From manderse at redhat.com  Tue Mar 10 03:00:58 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Tue, 10 Mar 2015 03:00:58 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201503100700.t2A70wCA016315@int-mx14.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-19422

https://issues.jboss.org/browse/JBIDE-19422
Summary: Maven project import fails when portlet configurator fails to detect Seam

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 20:32:42.021235

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From manderse at redhat.com  Wed Mar 11 03:01:46 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Wed, 11 Mar 2015 03:01:46 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201503110701.t2B71klt009568@int-mx11.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBDS-3371

https://issues.jboss.org/browse/JBDS-3371
Summary: The method openFileDialog(null, null) is undefined for the type FileOpenService

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 10:03:46.553192

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From nboldt at redhat.com  Wed Mar 11 12:23:29 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 11 Mar 2015 12:23:29 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Reminder,
 code freeze for JBT 4.2.3.CR1 / JBDS 8.1.0.CR1 is tomorrow
Message-ID: <55006C01.6010301@redhat.com>

Please make sure you're using the latest 4.2.3.CR1-SNAPSHOT parent pom 
in your builds, in order to pick up the latest 4.42.0.Final-SNAPSHOT 
target platform.

If you've contributed fixes to 4.2.3.CR1 (since 4.2.3.Beta1) and your 
job is NOT currently enabled, please remember to do so, or at least to 
tell me so I can do so for you.

More nags tomorrow!

Cheers,

Nick

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From pleacu at redhat.com  Wed Mar 11 17:19:30 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Wed, 11 Mar 2015 17:19:30 -0400 (EDT)
Subject: [jbosstools-dev] JBDSIS 8.0.0.GA/ JBTIS 4.2.0.Final now live
In-Reply-To: <845752270.25180120.1426089569218.JavaMail.zimbra@redhat.com>
Message-ID: <269839011.25343222.1426108770008.JavaMail.zimbra@redhat.com>


   Greetings,
      The latest Eclipse-Luna capable, JBDS 8.0.2.GA compatible Integration Stack GA tooling is
   released.  This capture contains the product release of the JBoss Data Virtualization tooling
   (ModeShape, Teiid Designer) and Early Access component version updates.

   JBDSIS 8.0.0.GA, JBTIS 4.2.0.Final

      1. If installing from Eclipse Luna:
          Help > Eclipse Marketplace...
          - in the 'Search' tab enter 'jbds' in the 'Find' input widget
          - select the 'Go' button
          - install 'Red Hat JBoss Developer Studio 8.0.2.GA'

      2. Start jbdevstudio or eclipse (with jbds from step 1)

      3. Select the Software/Update tab in the JBoss Central view.  The Data Virtualization tooling will be
         immediately visible.  Check the "Enable Early Access" check box to see the remainder of the integration
         stack components.

      done!

   The standard p2 installer is also available for JBDSIS:

     1. If installing from Eclipse Luna:
          Help > Eclipse Marketplace...
          - in the 'Search' tab enter 'jbds' in the 'Find' input widget
          - select the 'Go' button
          - install 'Red Hat JBoss Developer Studio 8.0.2.GA'

      2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
          Help > Install New Software...
          Add...
          - use this for 'Location:' for the production integration stack:
            https://devstudio.redhat.com/updates/8.0/integration-stack/

          - use this for 'Location:' for the early access integration stack:
            https://devstudio.redhat.com/updates/8.0/integration-stack/earlyaccess/

   The standard p2 installer is available for the .Final community capture and Early Access (JBTIS):

      * Start eclipse-with-jboss-tools, then:
          Help > Install New Software...
          Add...

          - use this for 'Location:' for the released-components integration stack:
            http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/

          - use this for 'Location:' for the early access integration stack:
            http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/earlyaccess

   JBoss Central is supported for the .Final community capture and Early Access (JBTIS):

      * Install JBoss Tools 4.2.1.Final:
          Help > Eclipse Marketplace...
          - in the 'Search' tab enter 'jboss tools' in the 'Find' input widget
          - select the 'Go' button
          - install 'JBoss Tools 4.2.1.Final'
  
      * Use JBoss Central - community bits are live
        ./eclipse

   The standalone p2 installer is available for the community capture (JBTIS):

      * Start eclipse Luna, then:
          Help > Install New Software...
          Add...
          - use this for 'Location:' for the .Final integration stack:
            http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/4.2.0.Final/withreferences/

          - use this for 'Location:' for the early access integration stack:
            http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/4.2.0.Final/earlyaccess/withreferences/

   Offline zip files are supported for both production and community installs:

      1. http://www.qa.jboss.com/binaries/RHDS/updates/stable/luna/integration-stack/aggregate/devstudio-integration-stack-aggregate-8.0.0.GA.zip
         http://www.qa.jboss.com/binaries/RHDS/updates/stable/luna/integration-stack/aggregate/devstudio-integration-stack-aggregate-8.0.0.GA.zip.MD5

      2. http://www.qa.jboss.com/binaries/RHDS/updates/stable/luna/integration-stack/aggregate/devstudio-integration-stack-aggregate-8.0.0.GA-earlyaccess.zip
         http://www.qa.jboss.com/binaries/RHDS/updates/stable/luna/integration-stack/aggregate/devstudio-integration-stack-aggregate-8.0.0.GA-earlyaccess.zip.MD5

      3. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.0.Final.zip
         http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.0.Final.zip.MD5

      4. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.0.Final-earlyaccess.zip
         http://download.jboss.org/jbosstools/updates/stable/luna/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.2.0.Final-earlyaccess.zip.MD5

   For component and QE test developers - the JBTIS target platforms are:

      - Full and candidate release target platforms including early access dependencies:
      https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.2.1.Final/  # note -ea target files
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Final/jbtis/REPO/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Final/jbtis/earlyaccess/REPO/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Final/jbdsis/REPO/
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Final/jbdsis/earlyaccess/REPO/


   Blog pending...

   Give it a try!
         --paull

From nboldt at redhat.com  Thu Mar 12 12:15:22 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 12 Mar 2015 12:15:22 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Code Freeze for 4.2.3.CR1 /
	8.1.0.CR1 is on now
Message-ID: <5501BB9A.1060606@redhat.com>

If your project is contributing to this CR1 release, please ensure 
you've pushed in the commits before EOD today, upversioned as needed, 
and are using the latest 4.2.3.CR1-SNAPSHOT parent pom.

Currently, I am tracking 8 projects' changes for CR1 - if your project 
is NOT on this list, and you plan to slide something in for CR1, *PLEASE 
LET ME KNOW TODAY*.

Base
Server
Javaee
Hibernate
Forge
Aerogear
Webservices
  and
Central

Of those, the first 7 were built last night or this morning and are blue 
in Jenkins [1], [2]. Central is blue because the commit(s) for this 
release have not been pushed to the 4.2.x branch yet [3].

Giddyup, Central. :D

[1] 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/
[2] 
http://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.2.luna/ 
[only shows last week's builds due to publishing lag] :(
[3] 
https://github.com/jbosstools/jbosstools-central/commits/jbosstools-4.2.x

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From nboldt at redhat.com  Thu Mar 12 17:19:59 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 12 Mar 2015 17:19:59 -0400
Subject: [jbosstools-dev] FYI: parent pom variable jbosstools-site-stream
 has been renamed to jbosstools_stream in master branch
Message-ID: <550202FF.8060104@redhat.com>

TL;DR:

jbosstools-site-stream is now jbosstools_stream; if you use 
jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.

---

I've had to rename the parent pom Maven variable 
<jbosstools-site-stream> in order to reuse it in Jenkins job configs. 
This allows us to override it in Jenkins AND use the same value in shell 
scripts to define where content is published on the server, as per the 
new reorg going on for JBT 4.3 / JBDS 9 [1].

The new variable is jbosstools_stream; I intentionally renamed it rather 
than just swapping dashes (not allowed in bash variables) for 
underscores (allowed) so it would be more obvious.

[1] https://issues.jboss.org/browse/JBDS-3208

As far as I can tell, the only affected projects are:

jbosstools-build [2]
jbosstools-central [3]
jbosstools-integration-tests [4]
jbdevstudio-product [5]

[2] https://github.com/jbosstools/jbosstools-build/pull/178
[3] https://github.com/jbosstools/jbosstools-central/pull/325
[4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
[5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280

Note that the old variable is *still in the parent pom*, but it is now 
deprecated & derived from the the new one [6]. 	

[6] 
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From manderse at redhat.com  Thu Mar 12 22:49:10 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 12 Mar 2015 22:49:10 -0400 (EDT)
Subject: [jbosstools-dev] FYI: parent pom variable
	jbosstools-site-stream has been renamed to jbosstools_stream
	in master branch
In-Reply-To: <550202FF.8060104@redhat.com>
References: <550202FF.8060104@redhat.com>
Message-ID: <BFF96C58-BD07-4A10-AE70-505762DE38E2@redhat.com>

Why are we both renaming and changing this with risk of breaking defaults override ?

And why can't you set it from the script with the old name ? 

If you can't use x-y-z why not just in the shell script use x_y_z ? 

That seems way less intrusive ?



/max
http://about.me/maxandersen


> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
> 
> TL;DR:
> 
> jbosstools-site-stream is now jbosstools_stream; if you use 
> jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.
> 
> ---
> 
> I've had to rename the parent pom Maven variable 
> <jbosstools-site-stream> in order to reuse it in Jenkins job configs. 
> This allows us to override it in Jenkins AND use the same value in shell 
> scripts to define where content is published on the server, as per the 
> new reorg going on for JBT 4.3 / JBDS 9 [1].
> 
> The new variable is jbosstools_stream; I intentionally renamed it rather 
> than just swapping dashes (not allowed in bash variables) for 
> underscores (allowed) so it would be more obvious.
> 
> [1] https://issues.jboss.org/browse/JBDS-3208
> 
> As far as I can tell, the only affected projects are:
> 
> jbosstools-build [2]
> jbosstools-central [3]
> jbosstools-integration-tests [4]
> jbdevstudio-product [5]
> 
> [2] https://github.com/jbosstools/jbosstools-build/pull/178
> [3] https://github.com/jbosstools/jbosstools-central/pull/325
> [4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
> 
> Note that the old variable is *still in the parent pom*, but it is now 
> deprecated & derived from the the new one [6].    
> 
> [6] 
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From manderse at redhat.com  Thu Mar 12 22:56:33 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 12 Mar 2015 22:56:33 -0400 (EDT)
Subject: [jbosstools-dev] FYI: parent pom variable
	jbosstools-site-stream has been renamed to jbosstools_stream
	in master branch
In-Reply-To: <550202FF.8060104@redhat.com>
References: <550202FF.8060104@redhat.com>
Message-ID: <3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>

I just tried and I don't see any problems using x-y-z in neither Jenkins or scripts. 

Can you elaborate more please ?

/max
http://about.me/maxandersen


> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
> 
> TL;DR:
> 
> jbosstools-site-stream is now jbosstools_stream; if you use 
> jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.
> 
> ---
> 
> I've had to rename the parent pom Maven variable 
> <jbosstools-site-stream> in order to reuse it in Jenkins job configs. 
> This allows us to override it in Jenkins AND use the same value in shell 
> scripts to define where content is published on the server, as per the 
> new reorg going on for JBT 4.3 / JBDS 9 [1].
> 
> The new variable is jbosstools_stream; I intentionally renamed it rather 
> than just swapping dashes (not allowed in bash variables) for 
> underscores (allowed) so it would be more obvious.
> 
> [1] https://issues.jboss.org/browse/JBDS-3208
> 
> As far as I can tell, the only affected projects are:
> 
> jbosstools-build [2]
> jbosstools-central [3]
> jbosstools-integration-tests [4]
> jbdevstudio-product [5]
> 
> [2] https://github.com/jbosstools/jbosstools-build/pull/178
> [3] https://github.com/jbosstools/jbosstools-central/pull/325
> [4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
> 
> Note that the old variable is *still in the parent pom*, but it is now 
> deprecated & derived from the the new one [6].    
> 
> [6] 
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From nboldt at redhat.com  Fri Mar 13 00:32:39 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 13 Mar 2015 00:32:39 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: please use the latest JBT
 4.3.0.Alpha2 parent pom in your root pom
Message-ID: <55026867.5050002@redhat.com>

In order to be able to build Alpha2 correctly using the new dir 
structure (JBDS-3206), we need to have everyone bump their root poms to 
use the Alpha2 parent pom.

Here are a few PRs for the projects that haven't already moved to Alpha2:

https://github.com/jbosstools/jbosstools-aerogear/pull/128
https://github.com/jbosstools/jbosstools-arquillian/pull/109
https://github.com/jbosstools/jbosstools-birt/pull/34
https://github.com/jbosstools/jbosstools-browsersim/pull/60
https://github.com/jbosstools/jbosstools-forge/pull/137
https://github.com/jbosstools/jbosstools-freemarker/pull/31
https://github.com/jbosstools/jbosstools-hibernate/pull/69
https://github.com/jbosstools/jbosstools-livereload/pull/85
https://github.com/jbosstools/jbosstools-portlet/pull/31
https://github.com/jbosstools/jbosstools-server/pull/334
https://github.com/jbosstools/jbosstools-vpe/pull/299
https://github.com/jbosstools/jbosstools-webservices/pull/230

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From nboldt at redhat.com  Fri Mar 13 00:33:40 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 13 Mar 2015 00:33:40 -0400
Subject: [jbosstools-dev] FYI: parent pom variable
 jbosstools-site-stream has been renamed to jbosstools_stream in master
 branch
In-Reply-To: <3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
References: <550202FF.8060104@redhat.com>
	<3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
Message-ID: <550268A4.9000706@redhat.com>

You can't do shell expansion of variables with dashes in the name.

$ jbosstools-site-stream=4.3.mars
bash: jbosstools-site-stream=4.3.mars: command not found

$ set jbosstools-site-stream=4.3.mars
$ echo ${jbosstools-site-stream}
site-stream

$ export jbosstools-site-stream=4.3.mars
bash: export: `jbosstools-site-stream=4.3.mars': not a valid identifier

More: 
http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character

So... it doesn't work.

But if you prefer I can use jbosstools_site_stream instead of 
jbosstools_stream. Either way the old one is set to the new one [1] so 
that old jobs can keep using the deprecated one.

[1] 
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76


On 03/12/2015 10:56 PM, Max Rydahl Andersen wrote:
> I just tried and I don't see any problems using x-y-z in neither Jenkins or scripts.
>
> Can you elaborate more please ?
>
> /max
> http://about.me/maxandersen
>
>
>> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
>>
>> TL;DR:
>>
>> jbosstools-site-stream is now jbosstools_stream; if you use
>> jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.
>>
>> ---
>>
>> I've had to rename the parent pom Maven variable
>> <jbosstools-site-stream> in order to reuse it in Jenkins job configs.
>> This allows us to override it in Jenkins AND use the same value in shell
>> scripts to define where content is published on the server, as per the
>> new reorg going on for JBT 4.3 / JBDS 9 [1].
>>
>> The new variable is jbosstools_stream; I intentionally renamed it rather
>> than just swapping dashes (not allowed in bash variables) for
>> underscores (allowed) so it would be more obvious.
>>
>> [1] https://issues.jboss.org/browse/JBDS-3208
>>
>> As far as I can tell, the only affected projects are:
>>
>> jbosstools-build [2]
>> jbosstools-central [3]
>> jbosstools-integration-tests [4]
>> jbdevstudio-product [5]
>>
>> [2] https://github.com/jbosstools/jbosstools-build/pull/178
>> [3] https://github.com/jbosstools/jbosstools-central/pull/325
>> [4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
>> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
>>
>> Note that the old variable is *still in the parent pom*, but it is now
>> deprecated & derived from the the new one [6].
>>
>> [6]
>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at 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

From xcoulon at redhat.com  Fri Mar 13 04:45:42 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Fri, 13 Mar 2015 09:45:42 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: please use the latest JBT
	4.3.0.Alpha2 parent pom in your root pom
In-Reply-To: <55026867.5050002@redhat.com>
References: <55026867.5050002@redhat.com>
Message-ID: <2165596E-EDB6-41E3-A813-DE6B1E66A74A@redhat.com>

Thanks for the pull requests, Nick !

It's done for Webservices and LiveReload.

Best regards,
/Xavier



> On 13 Mar 2015, at 05:32, Nick Boldt <nboldt at redhat.com> wrote:
> 
> In order to be able to build Alpha2 correctly using the new dir 
> structure (JBDS-3206), we need to have everyone bump their root poms to 
> use the Alpha2 parent pom.
> 
> Here are a few PRs for the projects that haven't already moved to Alpha2:
> 
> https://github.com/jbosstools/jbosstools-aerogear/pull/128
> https://github.com/jbosstools/jbosstools-arquillian/pull/109
> https://github.com/jbosstools/jbosstools-birt/pull/34
> https://github.com/jbosstools/jbosstools-browsersim/pull/60
> https://github.com/jbosstools/jbosstools-forge/pull/137
> https://github.com/jbosstools/jbosstools-freemarker/pull/31
> https://github.com/jbosstools/jbosstools-hibernate/pull/69
> https://github.com/jbosstools/jbosstools-livereload/pull/85
> https://github.com/jbosstools/jbosstools-portlet/pull/31
> https://github.com/jbosstools/jbosstools-server/pull/334
> https://github.com/jbosstools/jbosstools-vpe/pull/299
> https://github.com/jbosstools/jbosstools-webservices/pull/230
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150313/9deeba0f/attachment.html 

From mmalina at redhat.com  Fri Mar 13 04:58:19 2015
From: mmalina at redhat.com (Martin Malina)
Date: Fri, 13 Mar 2015 09:58:19 +0100
Subject: [jbosstools-dev] FYI: parent pom variable
	jbosstools-site-stream has been renamed to jbosstools_stream
	in master branch
In-Reply-To: <550268A4.9000706@redhat.com>
References: <550202FF.8060104@redhat.com>
	<3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
	<550268A4.9000706@redhat.com>
Message-ID: <B9D59FF8-7DAC-4C95-B57E-709BF173092A@redhat.com>

I created a PR to change this in jbosstools-integration-tests.
https://github.com/jbosstools/jbosstools-integration-tests/pull/887 <https://github.com/jbosstools/jbosstools-integration-tests/pull/887>
So please keep us posted if it becomes something else eventually.

Thanks,
Martin


> On 13. 3. 2015, at 5:33, Nick Boldt <nboldt at redhat.com> wrote:
> 
> You can't do shell expansion of variables with dashes in the name.
> 
> $ jbosstools-site-stream=4.3.mars
> bash: jbosstools-site-stream=4.3.mars: command not found
> 
> $ set jbosstools-site-stream=4.3.mars
> $ echo ${jbosstools-site-stream}
> site-stream
> 
> $ export jbosstools-site-stream=4.3.mars
> bash: export: `jbosstools-site-stream=4.3.mars': not a valid identifier
> 
> More: 
> http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character
> 
> So... it doesn't work.
> 
> But if you prefer I can use jbosstools_site_stream instead of 
> jbosstools_stream. Either way the old one is set to the new one [1] so 
> that old jobs can keep using the deprecated one.
> 
> [1] 
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
> 
> 
> On 03/12/2015 10:56 PM, Max Rydahl Andersen wrote:
>> I just tried and I don't see any problems using x-y-z in neither Jenkins or scripts.
>> 
>> Can you elaborate more please ?
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>>> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
>>> 
>>> TL;DR:
>>> 
>>> jbosstools-site-stream is now jbosstools_stream; if you use
>>> jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.
>>> 
>>> ---
>>> 
>>> I've had to rename the parent pom Maven variable
>>> <jbosstools-site-stream> in order to reuse it in Jenkins job configs.
>>> This allows us to override it in Jenkins AND use the same value in shell
>>> scripts to define where content is published on the server, as per the
>>> new reorg going on for JBT 4.3 / JBDS 9 [1].
>>> 
>>> The new variable is jbosstools_stream; I intentionally renamed it rather
>>> than just swapping dashes (not allowed in bash variables) for
>>> underscores (allowed) so it would be more obvious.
>>> 
>>> [1] https://issues.jboss.org/browse/JBDS-3208
>>> 
>>> As far as I can tell, the only affected projects are:
>>> 
>>> jbosstools-build [2]
>>> jbosstools-central [3]
>>> jbosstools-integration-tests [4]
>>> jbdevstudio-product [5]
>>> 
>>> [2] https://github.com/jbosstools/jbosstools-build/pull/178
>>> [3] https://github.com/jbosstools/jbosstools-central/pull/325
>>> [4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
>>> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
>>> 
>>> Note that the old variable is *still in the parent pom*, but it is now
>>> deprecated & derived from the the new one [6].
>>> 
>>> [6]
>>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>> 
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150313/e9a666ce/attachment-0001.html 

From manderse at redhat.com  Fri Mar 13 10:59:00 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 13 Mar 2015 10:59:00 -0400 (EDT)
Subject: [jbosstools-dev] FYI: parent pom variable
	jbosstools-site-stream has been renamed to jbosstools_stream
	in master branch
In-Reply-To: <550268A4.9000706@redhat.com>
References: <550202FF.8060104@redhat.com>
	<3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
	<550268A4.9000706@redhat.com>
Message-ID: <6EEB0FB6-6BF2-46CF-8249-280CF416C3DC@redhat.com>

Why not just use the underscore form in the bash script that is said to be reduced/removed anyway and not have to do such sweeping changes in parent Pom and other locations just for what a bash script needs to do ? None of the poms will need to react/interact with the  variable as stored in the bash script. 

I see no value in introducing double the variables across parent Pom - we should be going towards *less* variations/duplications not more. 

Also I thought we had an agreement that parent Pom "api" changes was to at least be reviewed before applied - to reduce the amount of back and forth change in the part that potentially affects *all* projects. 

/max
http://about.me/maxandersen


> On 13 Mar 2015, at 05:33, Nick Boldt <nboldt at redhat.com> wrote:
> 
> You can't do shell expansion of variables with dashes in the name.
> 
> $ jbosstools-site-stream=4.3.mars
> bash: jbosstools-site-stream=4.3.mars: command not found
> 
> $ set jbosstools-site-stream=4.3.mars
> $ echo ${jbosstools-site-stream}
> site-stream
> 
> $ export jbosstools-site-stream=4.3.mars
> bash: export: `jbosstools-site-stream=4.3.mars': not a valid identifier
> 
> More: http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character
> 
> So... it doesn't work.
> 
> But if you prefer I can use jbosstools_site_stream instead of jbosstools_stream. Either way the old one is set to the new one [1] so that old jobs can keep using the deprecated one.
> 
> [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
> 
> 
>> On 03/12/2015 10:56 PM, Max Rydahl Andersen wrote:
>> I just tried and I don't see any problems using x-y-z in neither Jenkins or scripts.
>> 
>> Can you elaborate more please ?
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>>> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
>>> 
>>> TL;DR:
>>> 
>>> jbosstools-site-stream is now jbosstools_stream; if you use
>>> jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.
>>> 
>>> ---
>>> 
>>> I've had to rename the parent pom Maven variable
>>> <jbosstools-site-stream> in order to reuse it in Jenkins job configs.
>>> This allows us to override it in Jenkins AND use the same value in shell
>>> scripts to define where content is published on the server, as per the
>>> new reorg going on for JBT 4.3 / JBDS 9 [1].
>>> 
>>> The new variable is jbosstools_stream; I intentionally renamed it rather
>>> than just swapping dashes (not allowed in bash variables) for
>>> underscores (allowed) so it would be more obvious.
>>> 
>>> [1] https://issues.jboss.org/browse/JBDS-3208
>>> 
>>> As far as I can tell, the only affected projects are:
>>> 
>>> jbosstools-build [2]
>>> jbosstools-central [3]
>>> jbosstools-integration-tests [4]
>>> jbdevstudio-product [5]
>>> 
>>> [2] https://github.com/jbosstools/jbosstools-build/pull/178
>>> [3] https://github.com/jbosstools/jbosstools-central/pull/325
>>> [4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
>>> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
>>> 
>>> Note that the old variable is *still in the parent pom*, but it is now
>>> deprecated & derived from the the new one [6].
>>> 
>>> [6]
>>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>> 
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at 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


From manderse at redhat.com  Fri Mar 13 11:03:43 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 13 Mar 2015 11:03:43 -0400 (EDT)
Subject: [jbosstools-dev] FYI: parent pom variable
	jbosstools-site-stream has been renamed to jbosstools_stream
	in master branch
In-Reply-To: <550268A4.9000706@redhat.com>
References: <550202FF.8060104@redhat.com>
	<3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
	<550268A4.9000706@redhat.com>
Message-ID: <F70C9859-B3FA-45DB-AD8D-4DA7BBB785E9@redhat.com>

Also, this is not just one variable that has this form so it's a much bigger change that just a single property. 

On a loose count I saw over 24. 

/max
http://about.me/maxandersen


> On 13 Mar 2015, at 05:33, Nick Boldt <nboldt at redhat.com> wrote:
> 
> You can't do shell expansion of variables with dashes in the name.
> 
> $ jbosstools-site-stream=4.3.mars
> bash: jbosstools-site-stream=4.3.mars: command not found
> 
> $ set jbosstools-site-stream=4.3.mars
> $ echo ${jbosstools-site-stream}
> site-stream
> 
> $ export jbosstools-site-stream=4.3.mars
> bash: export: `jbosstools-site-stream=4.3.mars': not a valid identifier
> 
> More: http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character
> 
> So... it doesn't work.
> 
> But if you prefer I can use jbosstools_site_stream instead of jbosstools_stream. Either way the old one is set to the new one [1] so that old jobs can keep using the deprecated one.
> 
> [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
> 
> 
>> On 03/12/2015 10:56 PM, Max Rydahl Andersen wrote:
>> I just tried and I don't see any problems using x-y-z in neither Jenkins or scripts.
>> 
>> Can you elaborate more please ?
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>>> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
>>> 
>>> TL;DR:
>>> 
>>> jbosstools-site-stream is now jbosstools_stream; if you use
>>> jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.
>>> 
>>> ---
>>> 
>>> I've had to rename the parent pom Maven variable
>>> <jbosstools-site-stream> in order to reuse it in Jenkins job configs.
>>> This allows us to override it in Jenkins AND use the same value in shell
>>> scripts to define where content is published on the server, as per the
>>> new reorg going on for JBT 4.3 / JBDS 9 [1].
>>> 
>>> The new variable is jbosstools_stream; I intentionally renamed it rather
>>> than just swapping dashes (not allowed in bash variables) for
>>> underscores (allowed) so it would be more obvious.
>>> 
>>> [1] https://issues.jboss.org/browse/JBDS-3208
>>> 
>>> As far as I can tell, the only affected projects are:
>>> 
>>> jbosstools-build [2]
>>> jbosstools-central [3]
>>> jbosstools-integration-tests [4]
>>> jbdevstudio-product [5]
>>> 
>>> [2] https://github.com/jbosstools/jbosstools-build/pull/178
>>> [3] https://github.com/jbosstools/jbosstools-central/pull/325
>>> [4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
>>> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
>>> 
>>> Note that the old variable is *still in the parent pom*, but it is now
>>> deprecated & derived from the the new one [6].
>>> 
>>> [6]
>>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>> 
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at 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


From snjezana.peco at redhat.com  Fri Mar 13 11:09:01 2015
From: snjezana.peco at redhat.com (Snjezana Peco)
Date: Fri, 13 Mar 2015 16:09:01 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: please use the latest JBT
 4.3.0.Alpha2 parent pom in your root pom
In-Reply-To: <55026867.5050002@redhat.com>
References: <55026867.5050002@redhat.com>
Message-ID: <5502FD8D.9090600@redhat.com>

Done for arquillian, birt and portlet.

Snjeza

On 3/13/2015 5:32 AM, Nick Boldt wrote:
> In order to be able to build Alpha2 correctly using the new dir
> structure (JBDS-3206), we need to have everyone bump their root poms to
> use the Alpha2 parent pom.
>
> Here are a few PRs for the projects that haven't already moved to Alpha2:
>
> https://github.com/jbosstools/jbosstools-aerogear/pull/128
> https://github.com/jbosstools/jbosstools-arquillian/pull/109
> https://github.com/jbosstools/jbosstools-birt/pull/34
> https://github.com/jbosstools/jbosstools-browsersim/pull/60
> https://github.com/jbosstools/jbosstools-forge/pull/137
> https://github.com/jbosstools/jbosstools-freemarker/pull/31
> https://github.com/jbosstools/jbosstools-hibernate/pull/69
> https://github.com/jbosstools/jbosstools-livereload/pull/85
> https://github.com/jbosstools/jbosstools-portlet/pull/31
> https://github.com/jbosstools/jbosstools-server/pull/334
> https://github.com/jbosstools/jbosstools-vpe/pull/299
> https://github.com/jbosstools/jbosstools-webservices/pull/230
>


From ggastald at redhat.com  Fri Mar 13 12:24:46 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Fri, 13 Mar 2015 13:24:46 -0300
Subject: [jbosstools-dev] ACTION REQUIRED: please use the latest JBT
 4.3.0.Alpha2 parent pom in your root pom
In-Reply-To: <55026867.5050002@redhat.com>
References: <55026867.5050002@redhat.com>
Message-ID: <55030F4E.7000701@redhat.com>

Done for forge

On 03/13/2015 01:32 AM, Nick Boldt wrote:
> In order to be able to build Alpha2 correctly using the new dir
> structure (JBDS-3206), we need to have everyone bump their root poms to
> use the Alpha2 parent pom.
>
> Here are a few PRs for the projects that haven't already moved to Alpha2:
>
> https://github.com/jbosstools/jbosstools-aerogear/pull/128
> https://github.com/jbosstools/jbosstools-arquillian/pull/109
> https://github.com/jbosstools/jbosstools-birt/pull/34
> https://github.com/jbosstools/jbosstools-browsersim/pull/60
> https://github.com/jbosstools/jbosstools-forge/pull/137
> https://github.com/jbosstools/jbosstools-freemarker/pull/31
> https://github.com/jbosstools/jbosstools-hibernate/pull/69
> https://github.com/jbosstools/jbosstools-livereload/pull/85
> https://github.com/jbosstools/jbosstools-portlet/pull/31
> https://github.com/jbosstools/jbosstools-server/pull/334
> https://github.com/jbosstools/jbosstools-vpe/pull/299
> https://github.com/jbosstools/jbosstools-webservices/pull/230
>


From nboldt at redhat.com  Fri Mar 13 15:11:34 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 13 Mar 2015 15:11:34 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: please use the latest JBT
 4.3.0.Alpha2 parent pom in your root pom
In-Reply-To: <5502FD8D.9090600@redhat.com>
References: <55026867.5050002@redhat.com> <5502FD8D.9090600@redhat.com>
Message-ID: <55033666.7070800@redhat.com>

For future, if there are no changes in the code base, you can just 
reject PRs like this. Portlet has no changes for 4.3.0 - I'm not 
building it because it's still got the old version from 4.2.x and 
there's nothing new in it.

Sorry about that - should have just disabled your job instead. :(

Do you plan to do anything for Portlet in 4.3 / 8.1? Or is it a "dead 
project" like Freemarker?

N

On 03/13/2015 11:09 AM, Snjezana Peco wrote:
> Done for arquillian, birt and portlet.
>
> Snjeza
>
> On 3/13/2015 5:32 AM, Nick Boldt wrote:
>> In order to be able to build Alpha2 correctly using the new dir
>> structure (JBDS-3206), we need to have everyone bump their root poms to
>> use the Alpha2 parent pom.
>>
>> Here are a few PRs for the projects that haven't already moved to Alpha2:
>>
>> https://github.com/jbosstools/jbosstools-aerogear/pull/128
>> https://github.com/jbosstools/jbosstools-arquillian/pull/109
>> https://github.com/jbosstools/jbosstools-birt/pull/34
>> https://github.com/jbosstools/jbosstools-browsersim/pull/60
>> https://github.com/jbosstools/jbosstools-forge/pull/137
>> https://github.com/jbosstools/jbosstools-freemarker/pull/31
>> https://github.com/jbosstools/jbosstools-hibernate/pull/69
>> https://github.com/jbosstools/jbosstools-livereload/pull/85
>> https://github.com/jbosstools/jbosstools-portlet/pull/31
>> https://github.com/jbosstools/jbosstools-server/pull/334
>> https://github.com/jbosstools/jbosstools-vpe/pull/299
>> https://github.com/jbosstools/jbosstools-webservices/pull/230
>>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From nboldt at redhat.com  Fri Mar 13 15:19:32 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 13 Mar 2015 15:19:32 -0400
Subject: [jbosstools-dev] FYI: parent pom variable
 jbosstools-site-stream has been renamed to jbosstools_stream in master
 branch
In-Reply-To: <6EEB0FB6-6BF2-46CF-8249-280CF416C3DC@redhat.com>
References: <550202FF.8060104@redhat.com>
	<3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
	<550268A4.9000706@redhat.com>
	<6EEB0FB6-6BF2-46CF-8249-280CF416C3DC@redhat.com>
Message-ID: <55033844.2060403@redhat.com>

To restate the problem a 3rd time:

* Jenkins bash scripts (such as the newer, simpler, easier rsync.sh 
replacement for the crazy complicated publish.sh) can't expand a 
variable that's named with dashes.

* Parent pom uses variables with dashes.

* Therefore to use the SAME variable in Jenkins and in Maven, we need to 
rename the variable.

To explain the need for both jbosstools_stream and jbosstools-site-stream:

"I thought we had an agreement that parent Pom "api" changes was to at 
least be reviewed before applied."

And I agree with that. Therefore, to be able to move forward with the 
work I needed to do, I created this wrapper. The old one still works for 
Maven builds (but not for shell scripts). The new one works for both. 
Therefore the old (broken) API is respected and the new (better) API can 
be the way forward.

So, you were able to review, and I was able to verify my changes worked 
in Jenkins. It's a win-win, without delays!

"Why not just use the underscore form in the bash script?"

That's what I did. Renamed the variable in parent pom so I could reuse 
the same var across all jobs; had I not done that, we'd be passing 
jbosstools-site-stream to maven, and jbosstools_stream to bash, via two 
job parameters. Surely THAT would have been an ugly solution you would 
have reviewed and rejected?

Nick

On 03/13/2015 10:59 AM, Max Rydahl Andersen wrote:
> Why not just use the underscore form in the bash script that is said to be reduced/removed anyway and not have to do such sweeping changes in parent Pom and other locations just for what a bash script needs to do ? None of the poms will need to react/interact with the  variable as stored in the bash script.
>
> I see no value in introducing double the variables across parent Pom - we should be going towards *less* variations/duplications not more.
>
> Also I thought we had an agreement that parent Pom "api" changes was to at least be reviewed before applied - to reduce the amount of back and forth change in the part that potentially affects *all* projects.
>
> /max
> http://about.me/maxandersen
>
>
>> On 13 Mar 2015, at 05:33, Nick Boldt <nboldt at redhat.com> wrote:
>>
>> You can't do shell expansion of variables with dashes in the name.
>>
>> $ jbosstools-site-stream=4.3.mars
>> bash: jbosstools-site-stream=4.3.mars: command not found
>>
>> $ set jbosstools-site-stream=4.3.mars
>> $ echo ${jbosstools-site-stream}
>> site-stream
>>
>> $ export jbosstools-site-stream=4.3.mars
>> bash: export: `jbosstools-site-stream=4.3.mars': not a valid identifier
>>
>> More: http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character
>>
>> So... it doesn't work.
>>
>> But if you prefer I can use jbosstools_site_stream instead of jbosstools_stream. Either way the old one is set to the new one [1] so that old jobs can keep using the deprecated one.
>>
>> [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>
>>
>>> On 03/12/2015 10:56 PM, Max Rydahl Andersen wrote:
>>> I just tried and I don't see any problems using x-y-z in neither Jenkins or scripts.
>>>
>>> Can you elaborate more please ?
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>>
>>>> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
>>>>
>>>> TL;DR:
>>>>
>>>> jbosstools-site-stream is now jbosstools_stream; if you use
>>>> jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.
>>>>
>>>> ---
>>>>
>>>> I've had to rename the parent pom Maven variable
>>>> <jbosstools-site-stream> in order to reuse it in Jenkins job configs.
>>>> This allows us to override it in Jenkins AND use the same value in shell
>>>> scripts to define where content is published on the server, as per the
>>>> new reorg going on for JBT 4.3 / JBDS 9 [1].
>>>>
>>>> The new variable is jbosstools_stream; I intentionally renamed it rather
>>>> than just swapping dashes (not allowed in bash variables) for
>>>> underscores (allowed) so it would be more obvious.
>>>>
>>>> [1] https://issues.jboss.org/browse/JBDS-3208
>>>>
>>>> As far as I can tell, the only affected projects are:
>>>>
>>>> jbosstools-build [2]
>>>> jbosstools-central [3]
>>>> jbosstools-integration-tests [4]
>>>> jbdevstudio-product [5]
>>>>
>>>> [2] https://github.com/jbosstools/jbosstools-build/pull/178
>>>> [3] https://github.com/jbosstools/jbosstools-central/pull/325
>>>> [4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
>>>> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
>>>>
>>>> Note that the old variable is *still in the parent pom*, but it is now
>>>> deprecated & derived from the the new one [6].
>>>>
>>>> [6]
>>>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>>>
>>>> --
>>>> Nick Boldt :: JBoss by Red Hat
>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>> http://nick.divbyzero.com
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at 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

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From snjeza.peco at gmail.com  Fri Mar 13 16:50:48 2015
From: snjeza.peco at gmail.com (Snjezana Peco)
Date: Fri, 13 Mar 2015 21:50:48 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: please use the latest JBT
 4.3.0.Alpha2 parent pom in your root pom
In-Reply-To: <55033666.7070800@redhat.com>
References: <55026867.5050002@redhat.com> <5502FD8D.9090600@redhat.com>
	<55033666.7070800@redhat.com>
Message-ID: <55034DA8.2000404@gmail.com>

On 3/13/2015 8:11 PM, Nick Boldt wrote:
> For future, if there are no changes in the code base, you can just
> reject PRs like this. Portlet has no changes for 4.3.0 - I'm not
> building it because it's still got the old version from 4.2.x and
> there's nothing new in it.
>
> Sorry about that - should have just disabled your job instead. :(
>
> Do you plan to do anything for Portlet in 4.3 / 8.1?

No, we don't.

Snjeza


> Or is it a "dead
> project" like Freemarker?
> N
>
> On 03/13/2015 11:09 AM, Snjezana Peco wrote:
>> Done for arquillian, birt and portlet.
>>
>> Snjeza
>>
>> On 3/13/2015 5:32 AM, Nick Boldt wrote:
>>> In order to be able to build Alpha2 correctly using the new dir
>>> structure (JBDS-3206), we need to have everyone bump their root poms to
>>> use the Alpha2 parent pom.
>>>
>>> Here are a few PRs for the projects that haven't already moved to Alpha2:
>>>
>>> https://github.com/jbosstools/jbosstools-aerogear/pull/128
>>> https://github.com/jbosstools/jbosstools-arquillian/pull/109
>>> https://github.com/jbosstools/jbosstools-birt/pull/34
>>> https://github.com/jbosstools/jbosstools-browsersim/pull/60
>>> https://github.com/jbosstools/jbosstools-forge/pull/137
>>> https://github.com/jbosstools/jbosstools-freemarker/pull/31
>>> https://github.com/jbosstools/jbosstools-hibernate/pull/69
>>> https://github.com/jbosstools/jbosstools-livereload/pull/85
>>> https://github.com/jbosstools/jbosstools-portlet/pull/31
>>> https://github.com/jbosstools/jbosstools-server/pull/334
>>> https://github.com/jbosstools/jbosstools-vpe/pull/299
>>> https://github.com/jbosstools/jbosstools-webservices/pull/230
>>>


From rstryker at redhat.com  Sat Mar 14 05:21:50 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Sat, 14 Mar 2015 17:21:50 +0800
Subject: [jbosstools-dev] Any webkit  / internal browser masters around?
Message-ID: <5503FDAE.50100@redhat.com>

Hey all:

The internal browser view / browser editor when using WebKit (and 
Snjezana indicates other internal browser implementations as well) seems 
to be caching requests that they shouldn't.  The interesting thing here 
is that BrowserViewer  (used in both editor and view) are passing in 
"Cache-Control: no-cache" into the request, and yet the results are 
still being cached.   This seems to indicate that the underlying WebKit 
is ignoring this flag for some reason.


https://issues.jboss.org/browse/JBIDE-18685
https://bugs.eclipse.org/bugs/show_bug.cgi?id=448933

Is anyone experienced enough in the underlying APIs that can assist here 
in debugging or finding what in WebKit (or other browsers) is going 
wrong that they're ignoring this flag?  w3.org documentation indicates 
these flags should *never* be ignored:

http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html


14.9 Cache-Control

The Cache-Control general-header field is used to specify directives 
that MUST be obeyed by all caching mechanisms along the request/response 
chain. The directives specify behavior intended to prevent caches from 
adversely interfering with the request or response. These directives 
typically override the default caching algorithms. Cache directives are 
unidirectional in that the presence of a directive in a request does not 
imply that the same directive is to be given in the response.


This could be a  bug in webkit, or in how the internal browser is 
communicating with webkit, but I seem to be out of my area of expertise 
trying to drill down into the JNI commands and webkit proper.

Anyone have any ideas or experience in this area?

- Rob Stryker

From manderse at redhat.com  Sat Mar 14 06:56:52 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Sat, 14 Mar 2015 03:56:52 -0700
Subject: [jbosstools-dev] parent pom variable jbosstools-site-stream has
 been renamed to jbosstools_stream in master branch
In-Reply-To: <55033844.2060403@redhat.com>
References: <550202FF.8060104@redhat.com>
	<3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
	<550268A4.9000706@redhat.com>
	<6EEB0FB6-6BF2-46CF-8249-280CF416C3DC@redhat.com>
	<55033844.2060403@redhat.com>
Message-ID: <A3A62E09-704F-4A3F-9D50-473B2C32A060@redhat.com>

On 13 Mar 2015, at 12:19, Nick Boldt wrote:

> To restate the problem a 3rd time:
>
> * Jenkins bash scripts (such as the newer, simpler, easier rsync.sh 
> replacement for the crazy complicated publish.sh) can't expand a 
> variable that's named with dashes.

that is not a problem. It is not sharing any logic/parameter passing 
with the parent pom.

> * Parent pom uses variables with dashes.

Yes, it actually by now has *alot* of naming conventions. It is a shame 
we don't just stick with one.

> * Therefore to use the SAME variable in Jenkins and in Maven, we need 
> to rename the variable.

No, you don't need to give it a new *name*, just have it use _ in bash 
and - in parent pom and
things would not be perfect but they would be easily understood/mapped 
and not need any kind of broad change.

> To explain the need for both jbosstools_stream and 
> jbosstools-site-stream:
>
> "I thought we had an agreement that parent Pom "api" changes was to at 
> least be reviewed before applied."
>
> And I agree with that. Therefore, to be able to move forward with the 
> work I needed to do, I created this wrapper.
> The old one still works for Maven builds (but not for shell scripts). 
> The new one works for both. Therefore the old (broken) API is 
> respected and the new (better) API can be the way forward.
>
> So, you were able to review, and I was able to verify my changes 
> worked in Jenkins. It's a win-win, without delays!

I'm sorry but you did *not* need to create a wrapper, you could just us 
easily have used jbosstools_site_stream in the bash scripts.
I'm simply not following where this ever would be a problem.

Also a review implies that things don't go into master and result in 
mails asking for everyone to do a non-reviewed change - that is exactly
what will cause a delay if there is some easy to fix before going live 
fix.

> "Why not just use the underscore form in the bash script?"
>
> That's what I did. Renamed the variable in parent pom so I could reuse 
> the same var across all jobs; had I not done that, we'd be passing 
> jbosstools-site-stream to maven, and jbosstools_stream to bash, via 
> two job parameters. Surely THAT would have been an ugly solution you 
> would have reviewed and rejected?

I simply do not follow why you need *two* job parameters for that. The 
jenkins job just need to have *one* (call it "jbosstools-site-stream" 
and when the mvn script is called you do mvn 
-Djbosstools-site-stream=${jbosstools-site-stream} and when using bash 
you do syncstuff.sh jbosstools_site_stream=${jbosstools-site-stream}

That is completely clean.
No renames, just a - replaced with _ and no broad changes needed in 
parent pom nor in all affected projects and avoided subtle different 
between or branches/builds.

Also you only wrote this as jbosstools-site-stream changes, but it also 
(for consistency) would affect all the repository references for each 
component build.

So yeah, most definitely I would have accepted the simplest and less 
intrusive fix where it is *only* the bash script that has a different 
change.

Can we get it back to the minimal change in master instead of this big 
broad one, please ?

/max
http://about.me/maxandersen

From manderse at redhat.com  Sat Mar 14 07:00:28 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Sat, 14 Mar 2015 04:00:28 -0700
Subject: [jbosstools-dev] Any webkit / internal browser masters around?
In-Reply-To: <5503FDAE.50100@redhat.com>
References: <5503FDAE.50100@redhat.com>
Message-ID: <19EE4192-4289-49E2-AFE8-80B0D74551AB@redhat.com>

Google searching says its a known bug in safari/webkit:

http://stackoverflow.com/questions/3602887/why-doesnt-safari-honor-my-cache-control-directive

https://bugs.webkit.org/show_bug.cgi?id=71509

https://bugs.webkit.org/show_bug.cgi?id=85562

so seems like no way to avoid it.
/max

> Hey all:
>
> The internal browser view / browser editor when using WebKit (and
> Snjezana indicates other internal browser implementations as well) 
> seems
> to be caching requests that they shouldn't.  The interesting thing 
> here
> is that BrowserViewer  (used in both editor and view) are passing in
> "Cache-Control: no-cache" into the request, and yet the results are
> still being cached.   This seems to indicate that the underlying 
> WebKit
> is ignoring this flag for some reason.
>
>
> https://issues.jboss.org/browse/JBIDE-18685
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=448933
>
> Is anyone experienced enough in the underlying APIs that can assist 
> here
> in debugging or finding what in WebKit (or other browsers) is going
> wrong that they're ignoring this flag?  w3.org documentation indicates
> these flags should *never* be ignored:
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
>
>
> 14.9 Cache-Control
>
> The Cache-Control general-header field is used to specify directives
> that MUST be obeyed by all caching mechanisms along the 
> request/response
> chain. The directives specify behavior intended to prevent caches from
> adversely interfering with the request or response. These directives
> typically override the default caching algorithms. Cache directives 
> are
> unidirectional in that the presence of a directive in a request does 
> not
> imply that the same directive is to be given in the response.
>
>
> This could be a  bug in webkit, or in how the internal browser is
> communicating with webkit, but I seem to be out of my area of 
> expertise
> trying to drill down into the JNI commands and webkit proper.
>
> Anyone have any ideas or experience in this area?
>
> - Rob Stryker
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From nboldt at redhat.com  Sat Mar 14 17:07:29 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Sat, 14 Mar 2015 17:07:29 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.2.3.CR1 bits available for
	community & QE testing
Message-ID: <5504A311.3050607@redhat.com>

As always, these are not FINAL bits, but preliminary results for 
community & QE testing. Not for use by customers or end users.

Update site: http://download.jboss.org/jbosstools/updates/staging/luna/

Target platforms:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Final 

* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.42.0.Final-SNAPSHOT 


Until the above target platform site is released, you may need to add it 
to Eclipse to resolve dependencies at install time.
Once released, dependencies will be found automatically from here:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ 
(latest release)
* 
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.42.0.CR1-SNAPSHOT/ 
(upcoming milestone)
* 
http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.42.0.CR1-SNAPSHOT/ 
(upcoming milestone)

New + noteworthy (subject to change):
* 
https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
* http://tools.jboss.org/documentation/whatsnew/

Schedule: 
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel

--

Additional update sites:
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.CR1-updatesite-core/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.CR1-updatesite-coretests/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.CR1-updatesite-hibernatetools/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.CR1-updatesite-webtools/
and build sites:
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.CR1-build-core/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.CR1-build-coretests/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.CR1-build-hibernatetools/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.CR1-build-webtools/

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From rstryker at redhat.com  Mon Mar 16 04:30:25 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Mon, 16 Mar 2015 16:30:25 +0800
Subject: [jbosstools-dev] PTO March 19th to April 4
Message-ID: <550694A1.7070801@redhat.com>

Hi All:

I'm on PTO from March 19th to April 4th.   Just keep opening bugs for me 
and I'll fix them when I get back :D

- Rob

From rstryker at redhat.com  Mon Mar 16 05:07:43 2015
From: rstryker at redhat.com (Rob Stryker)
Date: Mon, 16 Mar 2015 17:07:43 +0800
Subject: [jbosstools-dev] Facet support for eap6.x?
Message-ID: <55069D5F.1030602@redhat.com>

Hey all:

So about a year ago I bumped facet support for wildfly and eap6.x to 
include the jee7 facets.  See: 
https://github.com/jbosstools/jbosstools-server/commit/871c03d310bb85ea03d037d48ebe451f82f76179

Unfortunately there's no JIRA id attached to the commit.

Does anyone remember specifically asking me to enable some jee7 facets 
on eap6.1+ runtime? Or was this purely a mistake on my part? As I 
recall, there was a minor discussion where it was determined eap6.x was 
"partially compliant" and it was better to leave the facets enabled than 
not. But I can't find any written documentation of this at all, which is 
a failure on my part to not post summaries to any jiras.

- Rob Stryker

From manderse at redhat.com  Mon Mar 16 09:42:59 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 16 Mar 2015 14:42:59 +0100
Subject: [jbosstools-dev] Facet support for eap6.x?
In-Reply-To: <55069D5F.1030602@redhat.com>
References: <55069D5F.1030602@redhat.com>
Message-ID: <5D2FF55B-0EB8-4C8D-BCF4-2D3DED44DD6B@redhat.com>

websockets is a Java EE 7 feature but works on EAP6.

/max

> Hey all:
>
> So about a year ago I bumped facet support for wildfly and eap6.x to
> include the jee7 facets.  See:
> https://github.com/jbosstools/jbosstools-server/commit/871c03d310bb85ea03d037d48ebe451f82f76179
>
> Unfortunately there's no JIRA id attached to the commit.
>
> Does anyone remember specifically asking me to enable some jee7 facets
> on eap6.1+ runtime? Or was this purely a mistake on my part? As I
> recall, there was a minor discussion where it was determined eap6.x 
> was
> "partially compliant" and it was better to leave the facets enabled 
> than
> not. But I can't find any written documentation of this at all, which 
> is
> a failure on my part to not post summaries to any jiras.
>
> - Rob Stryker
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From nboldt at redhat.com  Mon Mar 16 09:52:44 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 16 Mar 2015 09:52:44 -0400
Subject: [jbosstools-dev] FYI: parent pom variable
 jbosstools-site-stream has been renamed to jbosstools_stream in master
 branch
In-Reply-To: <F70C9859-B3FA-45DB-AD8D-4DA7BBB785E9@redhat.com>
References: <550202FF.8060104@redhat.com>
	<3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
	<550268A4.9000706@redhat.com>
	<F70C9859-B3FA-45DB-AD8D-4DA7BBB785E9@redhat.com>
Message-ID: <5506E02C.4030109@redhat.com>

I only changed one, therefore it's a trivial update.

I never suggested we rename EVERYTHING. Just the variables we use both 
in Maven commandline and Jenkins. So far, the only one that I've seen in 
both which also can be used in bash scripts which handle publishing (the 
new simpler rsync.sh) is the variable for the stream (master vs. 4.3.mars).

Yes, we could rename all the vars that are affected, but many of them 
are only needed by Maven, and need not be reused when publishing / 
running shell scripts.

On 03/13/2015 11:03 AM, Max Rydahl Andersen wrote:
> Also, this is not just one variable that has this form so it's a much bigger change that just a single property.
>
> On a loose count I saw over 24.
>
> /max
> http://about.me/maxandersen
>
>
>> On 13 Mar 2015, at 05:33, Nick Boldt <nboldt at redhat.com> wrote:
>>
>> You can't do shell expansion of variables with dashes in the name.
>>
>> $ jbosstools-site-stream=4.3.mars
>> bash: jbosstools-site-stream=4.3.mars: command not found
>>
>> $ set jbosstools-site-stream=4.3.mars
>> $ echo ${jbosstools-site-stream}
>> site-stream
>>
>> $ export jbosstools-site-stream=4.3.mars
>> bash: export: `jbosstools-site-stream=4.3.mars': not a valid identifier
>>
>> More: http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character
>>
>> So... it doesn't work.
>>
>> But if you prefer I can use jbosstools_site_stream instead of jbosstools_stream. Either way the old one is set to the new one [1] so that old jobs can keep using the deprecated one.
>>
>> [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>
>>
>>> On 03/12/2015 10:56 PM, Max Rydahl Andersen wrote:
>>> I just tried and I don't see any problems using x-y-z in neither Jenkins or scripts.
>>>
>>> Can you elaborate more please ?
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>>
>>>> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
>>>>
>>>> TL;DR:
>>>>
>>>> jbosstools-site-stream is now jbosstools_stream; if you use
>>>> jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.
>>>>
>>>> ---
>>>>
>>>> I've had to rename the parent pom Maven variable
>>>> <jbosstools-site-stream> in order to reuse it in Jenkins job configs.
>>>> This allows us to override it in Jenkins AND use the same value in shell
>>>> scripts to define where content is published on the server, as per the
>>>> new reorg going on for JBT 4.3 / JBDS 9 [1].
>>>>
>>>> The new variable is jbosstools_stream; I intentionally renamed it rather
>>>> than just swapping dashes (not allowed in bash variables) for
>>>> underscores (allowed) so it would be more obvious.
>>>>
>>>> [1] https://issues.jboss.org/browse/JBDS-3208
>>>>
>>>> As far as I can tell, the only affected projects are:
>>>>
>>>> jbosstools-build [2]
>>>> jbosstools-central [3]
>>>> jbosstools-integration-tests [4]
>>>> jbdevstudio-product [5]
>>>>
>>>> [2] https://github.com/jbosstools/jbosstools-build/pull/178
>>>> [3] https://github.com/jbosstools/jbosstools-central/pull/325
>>>> [4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
>>>> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
>>>>
>>>> Note that the old variable is *still in the parent pom*, but it is now
>>>> deprecated & derived from the the new one [6].
>>>>
>>>> [6]
>>>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>>>
>>>> --
>>>> Nick Boldt :: JBoss by Red Hat
>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>> http://nick.divbyzero.com
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at 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

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From manderse at redhat.com  Mon Mar 16 11:46:51 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 16 Mar 2015 16:46:51 +0100
Subject: [jbosstools-dev] parent pom variable jbosstools-site-stream has
 been renamed to jbosstools_stream in master branch
In-Reply-To: <5506E02C.4030109@redhat.com>
References: <550202FF.8060104@redhat.com>
	<3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
	<550268A4.9000706@redhat.com>
	<F70C9859-B3FA-45DB-AD8D-4DA7BBB785E9@redhat.com>
	<5506E02C.4030109@redhat.com>
Message-ID: <145C410E-6EBB-47BB-A31B-626C85321944@redhat.com>

Then lets not do the change so we have consistent use of these, not a 
mix.

it really is not a problem using 
-Djbosstools-site-update=${jbosstools_site_update} IMO.

Zero change and consistent.

> I never suggested we rename EVERYTHING. Just the variables we use both 
> in Maven commandline and Jenkins. So far, the only one that I've seen 
> in both which also can be used in bash scripts which handle publishing 
> (the new simpler rsync.sh) is the variable for the stream (master vs. 
> 4.3.mars).
>
> Yes, we could rename all the vars that are affected, but many of them 
> are only needed by Maven, and need not be reused when publishing / 
> running shell scripts.

I use the site references to ensure all content is build and pushed 
to/from local machine.

/max

> On 03/13/2015 11:03 AM, Max Rydahl Andersen wrote:
>> Also, this is not just one variable that has this form so it's a much 
>> bigger change that just a single property.
>>
>> On a loose count I saw over 24.
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>>> On 13 Mar 2015, at 05:33, Nick Boldt <nboldt at redhat.com> wrote:
>>>
>>> You can't do shell expansion of variables with dashes in the name.
>>>
>>> $ jbosstools-site-stream=4.3.mars
>>> bash: jbosstools-site-stream=4.3.mars: command not found
>>>
>>> $ set jbosstools-site-stream=4.3.mars
>>> $ echo ${jbosstools-site-stream}
>>> site-stream
>>>
>>> $ export jbosstools-site-stream=4.3.mars
>>> bash: export: `jbosstools-site-stream=4.3.mars': not a valid 
>>> identifier
>>>
>>> More: 
>>> http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character
>>>
>>> So... it doesn't work.
>>>
>>> But if you prefer I can use jbosstools_site_stream instead of 
>>> jbosstools_stream. Either way the old one is set to the new one [1] 
>>> so that old jobs can keep using the deprecated one.
>>>
>>> [1] 
>>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>>
>>>
>>>> On 03/12/2015 10:56 PM, Max Rydahl Andersen wrote:
>>>> I just tried and I don't see any problems using x-y-z in neither 
>>>> Jenkins or scripts.
>>>>
>>>> Can you elaborate more please ?
>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>>
>>>>
>>>>> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
>>>>>
>>>>> TL;DR:
>>>>>
>>>>> jbosstools-site-stream is now jbosstools_stream; if you use
>>>>> jbosstools-site-stream, please update your poms/jobs for JBT 
>>>>> 4.3/JBDS 9.
>>>>>
>>>>> ---
>>>>>
>>>>> I've had to rename the parent pom Maven variable
>>>>> <jbosstools-site-stream> in order to reuse it in Jenkins job 
>>>>> configs.
>>>>> This allows us to override it in Jenkins AND use the same value in 
>>>>> shell
>>>>> scripts to define where content is published on the server, as per 
>>>>> the
>>>>> new reorg going on for JBT 4.3 / JBDS 9 [1].
>>>>>
>>>>> The new variable is jbosstools_stream; I intentionally renamed it 
>>>>> rather
>>>>> than just swapping dashes (not allowed in bash variables) for
>>>>> underscores (allowed) so it would be more obvious.
>>>>>
>>>>> [1] https://issues.jboss.org/browse/JBDS-3208
>>>>>
>>>>> As far as I can tell, the only affected projects are:
>>>>>
>>>>> jbosstools-build [2]
>>>>> jbosstools-central [3]
>>>>> jbosstools-integration-tests [4]
>>>>> jbdevstudio-product [5]
>>>>>
>>>>> [2] https://github.com/jbosstools/jbosstools-build/pull/178
>>>>> [3] https://github.com/jbosstools/jbosstools-central/pull/325
>>>>> [4] 
>>>>> https://github.com/jbosstools/jbosstools-integration-tests/pull/884
>>>>> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
>>>>>
>>>>> Note that the old variable is *still in the parent pom*, but it is 
>>>>> now
>>>>> deprecated & derived from the the new one [6].
>>>>>
>>>>> [6]
>>>>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>>>>
>>>>> --
>>>>> Nick Boldt :: JBoss by Red Hat
>>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>>> http://nick.divbyzero.com
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at 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
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


/max
http://about.me/maxandersen


From nboldt at redhat.com  Mon Mar 16 12:47:51 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 16 Mar 2015 12:47:51 -0400
Subject: [jbosstools-dev] parent pom variable jbosstools-site-stream has
 been renamed to jbosstools_stream in master branch
In-Reply-To: <145C410E-6EBB-47BB-A31B-626C85321944@redhat.com>
References: <550202FF.8060104@redhat.com>
	<3086A0E0-2A6B-41A2-8A4D-BEF2F55920B1@redhat.com>
	<550268A4.9000706@redhat.com>
	<F70C9859-B3FA-45DB-AD8D-4DA7BBB785E9@redhat.com>
	<5506E02C.4030109@redhat.com>
	<145C410E-6EBB-47BB-A31B-626C85321944@redhat.com>
Message-ID: <55070937.8080309@redhat.com>

TL;DR:

https://issues.jboss.org/browse/JBIDE-19458


On 03/16/2015 11:46 AM, Max Rydahl Andersen wrote:
> Then lets not do the change so we have consistent use of these, not a mix.
>
> it really is not a problem using
> -Djbosstools-site-update=${jbosstools_site_update} IMO.
>
> Zero change and consistent.
>
>> I never suggested we rename EVERYTHING. Just the variables we use both
>> in Maven commandline and Jenkins. So far, the only one that I've seen
>> in both which also can be used in bash scripts which handle publishing
>> (the new simpler rsync.sh) is the variable for the stream (master vs.
>> 4.3.mars).
>>
>> Yes, we could rename all the vars that are affected, but many of them
>> are only needed by Maven, and need not be reused when publishing /
>> running shell scripts.
>
> I use the site references to ensure all content is build and pushed
> to/from local machine.
>
> /max
>
>> On 03/13/2015 11:03 AM, Max Rydahl Andersen wrote:
>>> Also, this is not just one variable that has this form so it's a much
>>> bigger change that just a single property.
>>>
>>> On a loose count I saw over 24.
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>>
>>>> On 13 Mar 2015, at 05:33, Nick Boldt <nboldt at redhat.com> wrote:
>>>>
>>>> You can't do shell expansion of variables with dashes in the name.
>>>>
>>>> $ jbosstools-site-stream=4.3.mars
>>>> bash: jbosstools-site-stream=4.3.mars: command not found
>>>>
>>>> $ set jbosstools-site-stream=4.3.mars
>>>> $ echo ${jbosstools-site-stream}
>>>> site-stream
>>>>
>>>> $ export jbosstools-site-stream=4.3.mars
>>>> bash: export: `jbosstools-site-stream=4.3.mars': not a valid identifier
>>>>
>>>> More:
>>>> http://unix.stackexchange.com/questions/23659/can-shell-variable-include-character
>>>>
>>>>
>>>> So... it doesn't work.
>>>>
>>>> But if you prefer I can use jbosstools_site_stream instead of
>>>> jbosstools_stream. Either way the old one is set to the new one [1]
>>>> so that old jobs can keep using the deprecated one.
>>>>
>>>> [1]
>>>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>>>
>>>>
>>>>
>>>>> On 03/12/2015 10:56 PM, Max Rydahl Andersen wrote:
>>>>> I just tried and I don't see any problems using x-y-z in neither
>>>>> Jenkins or scripts.
>>>>>
>>>>> Can you elaborate more please ?
>>>>>
>>>>> /max
>>>>> http://about.me/maxandersen
>>>>>
>>>>>
>>>>>> On 12 Mar 2015, at 14:20, Nick Boldt <nboldt at redhat.com> wrote:
>>>>>>
>>>>>> TL;DR:
>>>>>>
>>>>>> jbosstools-site-stream is now jbosstools_stream; if you use
>>>>>> jbosstools-site-stream, please update your poms/jobs for JBT
>>>>>> 4.3/JBDS 9.
>>>>>>
>>>>>> ---
>>>>>>
>>>>>> I've had to rename the parent pom Maven variable
>>>>>> <jbosstools-site-stream> in order to reuse it in Jenkins job configs.
>>>>>> This allows us to override it in Jenkins AND use the same value in
>>>>>> shell
>>>>>> scripts to define where content is published on the server, as per
>>>>>> the
>>>>>> new reorg going on for JBT 4.3 / JBDS 9 [1].
>>>>>>
>>>>>> The new variable is jbosstools_stream; I intentionally renamed it
>>>>>> rather
>>>>>> than just swapping dashes (not allowed in bash variables) for
>>>>>> underscores (allowed) so it would be more obvious.
>>>>>>
>>>>>> [1] https://issues.jboss.org/browse/JBDS-3208
>>>>>>
>>>>>> As far as I can tell, the only affected projects are:
>>>>>>
>>>>>> jbosstools-build [2]
>>>>>> jbosstools-central [3]
>>>>>> jbosstools-integration-tests [4]
>>>>>> jbdevstudio-product [5]
>>>>>>
>>>>>> [2] https://github.com/jbosstools/jbosstools-build/pull/178
>>>>>> [3] https://github.com/jbosstools/jbosstools-central/pull/325
>>>>>> [4]
>>>>>> https://github.com/jbosstools/jbosstools-integration-tests/pull/884
>>>>>> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
>>>>>>
>>>>>> Note that the old variable is *still in the parent pom*, but it is
>>>>>> now
>>>>>> deprecated & derived from the the new one [6].
>>>>>>
>>>>>> [6]
>>>>>> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Nick Boldt :: JBoss by Red Hat
>>>>>> Productization Lead :: JBoss Tools & Dev Studio
>>>>>> http://nick.divbyzero.com
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at 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
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>
>
> /max
> http://about.me/maxandersen

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From nboldt at redhat.com  Wed Mar 18 09:25:40 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Wed, 18 Mar 2015 09:25:40 -0400
Subject: [jbosstools-dev] FYI: parent pom variable
 jbosstools-site-stream has been renamed to jbosstools_stream in master
 branch
In-Reply-To: <550202FF.8060104@redhat.com>
References: <550202FF.8060104@redhat.com>
Message-ID: <55097CD4.8020404@redhat.com>

After some discussion it's been decided to use jbosstools_site_stream 
instead of jbosstools_stream.

I've updated the PRs below (or created new ones) for the handful of 
affected projects.

Ref: https://issues.jboss.org/browse/JBIDE-19458

Apologies for the churn/confusion this may have caused.

N

On 03/12/2015 05:19 PM, Nick Boldt wrote:
> TL;DR:
>
> jbosstools-site-stream is now jbosstools_stream; if you use
> jbosstools-site-stream, please update your poms/jobs for JBT 4.3/JBDS 9.
>
> ---
>
> I've had to rename the parent pom Maven variable
> <jbosstools-site-stream> in order to reuse it in Jenkins job configs.
> This allows us to override it in Jenkins AND use the same value in shell
> scripts to define where content is published on the server, as per the
> new reorg going on for JBT 4.3 / JBDS 9 [1].
>
> The new variable is jbosstools_stream; I intentionally renamed it rather
> than just swapping dashes (not allowed in bash variables) for
> underscores (allowed) so it would be more obvious.
>
> [1] https://issues.jboss.org/browse/JBDS-3208
>
> As far as I can tell, the only affected projects are:
>
> jbosstools-build [2]
> jbosstools-central [3]
> jbosstools-integration-tests [4]
> jbdevstudio-product [5]
>
> [2] https://github.com/jbosstools/jbosstools-build/pull/178
> [3] https://github.com/jbosstools/jbosstools-central/pull/325
> [4] https://github.com/jbosstools/jbosstools-integration-tests/pull/884
> [5] https://github.com/jbdevstudio/jbdevstudio-product/pull/280
>
> Note that the old variable is *still in the parent pom*, but it is now
> deprecated & derived from the the new one [6].
>
> [6]
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L75-L76
>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From fbricon at gmail.com  Wed Mar 18 09:26:32 2015
From: fbricon at gmail.com (Fred Bricon)
Date: Wed, 18 Mar 2015 09:26:32 -0400
Subject: [jbosstools-dev] m2e 1.6 M6 to enable automatic update project
	configuration
Message-ID: <CAG2ouxQcOtyvOpAbYEURE5D8FhMTWENdYp414vWZEcQed8nRTg@mail.gmail.com>

Hi,

FYI, the latest m2e 1.6 CI build provides a way to automatically update
out-of-date project configuration [1].

We've been experimenting it for a while, as a standalone extension provided
by JBoss Tools Playground [2], and haven't faced any issue so far. So we
have decided to turn the workspace preference on by default (Preferences >
Maven > Automatically update Maven projects configuration (experimental))
[2].

You can install the latest CI build from [4], give it a try and let us know
how it works for you, good or bad.

Fred

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=335720
[2]
https://github.com/jbosstools/jbosstools-playground#auto-update-out-of-date-maven-project-configuration
[3] http://screencast.com/t/jOGEL5tt
[4] https://otto.takari.io/content/sites/m2e.extras/m2e/1.6.0/N/LATEST/

-- 
"Have you tried turning it off and on again" - The IT Crowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/85bcb6c3/attachment.html 

From jason at takari.io  Wed Mar 18 09:41:02 2015
From: jason at takari.io (Jason van Zyl)
Date: Wed, 18 Mar 2015 09:41:02 -0400
Subject: [jbosstools-dev] [m2e-users] m2e 1.6 M6 to enable automatic
	update project configuration
In-Reply-To: <CAG2ouxQcOtyvOpAbYEURE5D8FhMTWENdYp414vWZEcQed8nRTg@mail.gmail.com>
References: <CAG2ouxQcOtyvOpAbYEURE5D8FhMTWENdYp414vWZEcQed8nRTg@mail.gmail.com>
Message-ID: <2E2018AD-7EE9-4D50-BEA2-234D376225FE@takari.io>

Woo hoo! Thanks Fred!

On Mar 18, 2015, at 9:26 AM, Fred Bricon <fbricon at gmail.com> wrote:

> Hi,
> 
> FYI, the latest m2e 1.6 CI build provides a way to automatically update out-of-date project configuration [1]. 
> 
> We've been experimenting it for a while, as a standalone extension provided by JBoss Tools Playground [2], and haven't faced any issue so far. So we have decided to turn the workspace preference on by default (Preferences > Maven > Automatically update Maven projects configuration (experimental)) [2]. 
> 
> You can install the latest CI build from [4], give it a try and let us know how it works for you, good or bad.
> 
> Fred
> 
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=335720
> [2] https://github.com/jbosstools/jbosstools-playground#auto-update-out-of-date-maven-project-configuration
> [3] http://screencast.com/t/jOGEL5tt
> [4] https://otto.takari.io/content/sites/m2e.extras/m2e/1.6.0/N/LATEST/
> 
> -- 
> "Have you tried turning it off and on again" - The IT Crowd
> _______________________________________________
> m2e-users mailing list
> m2e-users at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------

There's no sense in being precise when you don't even know what you're talking about.

 -- John von Neumann













From mistria at redhat.com  Wed Mar 18 12:47:06 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 18 Mar 2015 17:47:06 +0100
Subject: [jbosstools-dev] Easymport documentation
Message-ID: <5509AC0A.7040906@redhat.com>

Hi all,

I've created a page of documentation about the basics of usage of what 
used to be called Easymport, and how to adopt it for new kinds of 
projects. See https://wiki.eclipse.org/E4/UI/Smart_Import
Please give it a try and report feedback, as we plan to have it part of 
JBDS 9, and to have it part of Platform UI for Mars+1 (Nirvana!)

Cheers,
-- 
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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/e52e3c01/attachment-0001.html 

From akazakov at exadel.com  Wed Mar 18 13:51:34 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Wed, 18 Mar 2015 10:51:34 -0700
Subject: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1,
	do we really need a respin?
Message-ID: <5509BB26.6090309@exadel.com>

Hi,

We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS 
8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
It prevents creating a forge addon. The workaround described in the JIRA.
The issue itself doesn't look like a blocker for JBDS 8.1 to me. 
However, George Gastaldi said that they are going to release a fixed 
Forge 2.15.2 today or tomorrow and *IF* we can do a respin for the forge 
component (with upgraded forge) *with no big cost* maybe it's worth doing.

WDYT?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/3a03d611/attachment.html 

From ldimaggi at redhat.com  Wed Mar 18 16:23:47 2015
From: ldimaggi at redhat.com (Len DiMaggio)
Date: Wed, 18 Mar 2015 16:23:47 -0400 (EDT)
Subject: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1,
	do we really need a respin?
In-Reply-To: <5509BB26.6090309@exadel.com>
References: <5509BB26.6090309@exadel.com>
Message-ID: <F27225E6-65F4-4640-A633-F7AEDE7C2AB3@redhat.com>

Would we want to pull in the fix and try to release CR1 at be end of the planned QE test cycle? We've already missed the 18th.  

--Len


(Sent from my iPhone)



> On Mar 18, 2015, at 1:52 PM, Alexey Kazakov <akazakov at exadel.com> wrote:
> 
> Hi,
> 
> We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS 8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
> It prevents creating a forge addon. The workaround described in the JIRA.
> The issue itself doesn't look like a blocker for JBDS 8.1 to me. However, George Gastaldi said that they are going to release a fixed Forge 2.15.2 today or tomorrow and IF we can do a respin for the forge component (with upgraded forge) with no big cost maybe it's worth doing.
> 
> WDYT?
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/4504bc1b/attachment.html 

From pleacu at redhat.com  Wed Mar 18 16:24:48 2015
From: pleacu at redhat.com (Paul Leacu)
Date: Wed, 18 Mar 2015 16:24:48 -0400 (EDT)
Subject: [jbosstools-dev] JBDSIS 7.1.0.GA/ JBTIS 4.1.7.Final now live
In-Reply-To: <922093330.28419124.1426684772347.JavaMail.zimbra@redhat.com>
Message-ID: <1236376747.28644157.1426710288025.JavaMail.zimbra@redhat.com>


   Greetings,
      The latest Eclipse-Kepler capable, JBDS 7.1.1.GA compatible Integration Stack GA tooling is
   released.  This release contains updated versions of the following components:

   * BPMN2          1.0.5
   * BPEL           1.0.4
   * Fuse Tooling   7.2.3
   * Teiid Designer 8.6.1

   JBDSIS 7.1.0.GA, JBTIS 4.1.7.Final

      1. If installing from Eclipse Kepler:
          Help > Eclipse Marketplace...
          - in the 'Search' tab enter 'jbds' in the 'Find' input widget
          - select the 'Go' button
          - install 'Red Hat JBoss Developer Studio 7.1.1.GA'

      2. Start jbdevstudio or eclipse (with jbds from step 1)

      3. Select the Software/Update tab in the JBoss Central view.  

      done!

   The standard p2 installer is also available for JBDSIS (.GA):

     1. If installing from Eclipse Kepler:
          Help > Eclipse Marketplace...
          - in the 'Search' tab enter 'jbds' in the 'Find' input widget
          - select the 'Go' button
          - install 'Red Hat JBoss Developer Studio 7.1.1.GA'

      2. Start jbdevstudio or eclipse-with-jbds from step 1, then:
          Help > Install New Software...
          Add...
          - use this for 'Location:' for the production integration stack:
            https://devstudio.redhat.com/updates/7.0/integration-stack/

   The standard p2 installer is available for JBTIS (.Final):

      * Start eclipse-with-jboss-tools, then:
          Help > Install New Software...
          Add...

          - use this for 'Location:' for the released-components integration stack:
            http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/

   JBoss Central is supported for JBTIS (.Final):

      1. Install JBoss Tools 4.1.2.Final:
          Help > Eclipse Marketplace...
          - in the 'Search' tab enter 'jboss tools' in the 'Find' input widget
          - select the 'Go' button
          - install 'JBoss Tools 4.1.2.Final'
  
      2. Select the Software/Update tab in the JBoss Central view.

   Offline zip files are supported for both production and community installs:

      1. https://devstudio.redhat.com/updates/7.0.0/jbdevstudio-integration-stack-updatesite-7.1.0.GA.zip
         https://devstudio.redhat.com/updates/7.0.0/jbdevstudio-integration-stack-updatesite-7.1.0.GA.zip.MD5

      2. http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.1.7.Final.zip
         http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/aggregate/jbosstools-integration-stack-aggregate-4.1.7.Final.zip.MD5

   For component and QE test developers - the JBTIS target platforms are:
      https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/tools/integration-stack/target-platform/4.1.11.Final/ 
      http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.11.Final/REPO/

   Blog pending...

   Give it a try!
         --paull

From akazakov at exadel.com  Wed Mar 18 16:44:28 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Wed, 18 Mar 2015 13:44:28 -0700
Subject: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1,
 do we really need a respin?
In-Reply-To: <F27225E6-65F4-4640-A633-F7AEDE7C2AB3@redhat.com>
References: <5509BB26.6090309@exadel.com>
	<F27225E6-65F4-4640-A633-F7AEDE7C2AB3@redhat.com>
Message-ID: <5509E3AC.1020502@exadel.com>

BTW what is QE status for CR1? I don't see any other issues reported in 
JIRA. How much time do you need to finish CR1 testing?


On 03/18/2015 01:23 PM, Len DiMaggio wrote:
> Would we want to pull in the fix and try to release CR1 at be end of 
> the planned QE test cycle? We've already missed the 18th.
>
> --Len
>
>
> (Sent from my iPhone)
>
>
>
> On Mar 18, 2015, at 1:52 PM, Alexey Kazakov <akazakov at exadel.com 
> <mailto:akazakov at exadel.com>> wrote:
>
>> Hi,
>>
>> We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS 
>> 8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
>> It prevents creating a forge addon. The workaround described in the JIRA.
>> The issue itself doesn't look like a blocker for JBDS 8.1 to me. 
>> However, George Gastaldi said that they are going to release a fixed 
>> Forge 2.15.2 today or tomorrow and *IF* we can do a respin for the 
>> forge component (with upgraded forge) *with no big cost* maybe it's 
>> worth doing.
>>
>> WDYT?
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/e3cd8b6f/attachment.html 

From nelsonm.tam at gmail.com  Wed Mar 18 16:49:19 2015
From: nelsonm.tam at gmail.com (Nelson Manuel Tam Urribarri)
Date: Wed, 18 Mar 2015 21:49:19 +0100
Subject: [jbosstools-dev] [m2e-users] m2e 1.6 M6 to enable automatic
	update project configuration
In-Reply-To: <CAG2ouxQcOtyvOpAbYEURE5D8FhMTWENdYp414vWZEcQed8nRTg@mail.gmail.com>
References: <CAG2ouxQcOtyvOpAbYEURE5D8FhMTWENdYp414vWZEcQed8nRTg@mail.gmail.com>
Message-ID: <CADnRVtb7MCdwFXOd_mQ3Sv32+DqJZCoO33ykQ8Rhs25G0HrT9w@mail.gmail.com>

Is a great news! Thanks for your very good work!
El 18/03/2015 14:27, "Fred Bricon" <fbricon at gmail.com> escribi?:

> Hi,
>
> FYI, the latest m2e 1.6 CI build provides a way to automatically update
> out-of-date project configuration [1].
>
> We've been experimenting it for a while, as a standalone extension
> provided by JBoss Tools Playground [2], and haven't faced any issue so far.
> So we have decided to turn the workspace preference on by default
> (Preferences > Maven > Automatically update Maven projects configuration
> (experimental)) [2].
>
> You can install the latest CI build from [4], give it a try and let us
> know how it works for you, good or bad.
>
> Fred
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=335720
> [2]
> https://github.com/jbosstools/jbosstools-playground#auto-update-out-of-date-maven-project-configuration
> [3] http://screencast.com/t/jOGEL5tt
> [4] https://otto.takari.io/content/sites/m2e.extras/m2e/1.6.0/N/LATEST/
>
> --
> "Have you tried turning it off and on again" - The IT Crowd
>
> _______________________________________________
> m2e-users mailing list
> m2e-users at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/4f928fec/attachment.html 

From manderse at redhat.com  Wed Mar 18 16:58:58 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 18 Mar 2015 21:58:58 +0100
Subject: [jbosstools-dev] Easymport documentation
In-Reply-To: <5509AC0A.7040906@redhat.com>
References: <5509AC0A.7040906@redhat.com>
Message-ID: <F68DF290-0A56-4B79-A64B-888B74533BCF@redhat.com>

On 18 Mar 2015, at 17:47, Mickael Istria wrote:

> Hi all,
>
> I've created a page of documentation about the basics of usage of what 
> used to be called Easymport, and how to adopt it for new kinds of 
> projects. See https://wiki.eclipse.org/E4/UI/Smart_Import
> Please give it a try and report feedback, as we plan to have it part 
> of JBDS 9, and to have it part of Platform UI for Mars+1 (Nirvana!)

Nice writeup.

Is the dependency on IResource removed for the initial scan yet so you 
dont have to create the top level project *always* ?

>
> Cheers,
> -- 
> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From fbricon at gmail.com  Wed Mar 18 19:45:24 2015
From: fbricon at gmail.com (Fred Bricon)
Date: Wed, 18 Mar 2015 19:45:24 -0400
Subject: [jbosstools-dev] Breaking changes to the archetype API -> m2e 2.0?
Message-ID: <CAG2ouxQ=+X4jq4BfXwG-uUd1braZyNucvdgdvKZ_FZ86g7RTAg@mail.gmail.com>

Hi,

I have an initial POC that uses maven-archetype-plugin 2.3, instead of the
2.0.alpha4 version (which was released in the 17th century, give or take).

I checked it fixes the following issues :
- https://bugs.eclipse.org/459453,
- https://bugs.eclipse.org/424010,
- https://bugs.eclipse.org/394918,
- https://bugs.eclipse.org/374660,
- https://bugs.eclipse.org/405945 (on OSX at least),
- https://bugs.eclipse.org/415114,
- https://bugs.eclipse.org/429287

Bugs https://bugs.eclipse.org/446657, https://bugs.eclipse.org/348893 may
or not be fixed (I can't test proxies)

Most of these issues were automatically closed already after 1 year of
inactivity. Doesn't mean the bugs are not there. My level of annoyance just
reached a point where I'd like to take action now.

The only problem with the archetype update is it will break 3rd party
adopters (JBoss Tools at least) depending on the archetype API
(package/class names changed between 2.0.alpha4 and 2.3). I don't plan on
introducing a compatibility layer, not worth the hassle IMHO.
Given that I'm also in charge of the JBoss Tools integration, I'm fine with
the impact :-)

Getting the fix in will require m2e to bump its version to 2.0 (and open a
bunch of CQs  in ipzilla)

I'd really like to get that change in for Eclipse Mars, if possible. Is it
too late from a release plan standpoint (i.e. 1.6 -> 2.0)? PMC, fellow m2e
committers wdyt?

Fred

-- 
"Have you tried turning it off and on again" - The IT Crowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/8c8aabc4/attachment-0001.html 

From ldimaggi at redhat.com  Wed Mar 18 20:29:11 2015
From: ldimaggi at redhat.com (Len DiMaggio)
Date: Wed, 18 Mar 2015 20:29:11 -0400 (EDT)
Subject: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1,
	do we really need a respin?
In-Reply-To: <5509E3AC.1020502@exadel.com>
References: <5509BB26.6090309@exadel.com>
	<F27225E6-65F4-4640-A633-F7AEDE7C2AB3@redhat.com>
	<5509E3AC.1020502@exadel.com>
Message-ID: <669DE092-5613-402E-9BDC-98094796F5CC@redhat.com>

The full test cycle will wrap up on the 26th - on schedule. 

The pre-can-we-release-the-CR1-build-ASAP testing was scheduled for 2 days - so we will finish that on March 19.  

--Len


(Sent from my iPhone)



> On Mar 18, 2015, at 4:44 PM, Alexey Kazakov <akazakov at exadel.com> wrote:
> 
> BTW what is QE status for CR1? I don't see any other issues reported in JIRA. How much time do you need to finish CR1 testing?
> 
> 
>> On 03/18/2015 01:23 PM, Len DiMaggio wrote:
>> Would we want to pull in the fix and try to release CR1 at be end of the planned QE test cycle? We've already missed the 18th.  
>> 
>> --Len
>> 
>> 
>> (Sent from my iPhone)
>> 
>> 
>> 
>> On Mar 18, 2015, at 1:52 PM, Alexey Kazakov <akazakov at exadel.com> wrote:
>> 
>>> Hi,
>>> 
>>> We have an issue in the latest Forge 2.15.1.Final (upgraded in           JBDS 8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
>>> It prevents creating a forge addon. The workaround described in the JIRA.
>>> The issue itself doesn't look like a blocker for JBDS 8.1 to me. However, George Gastaldi said that they are going to release a fixed Forge 2.15.2 today or tomorrow and IF we can do a respin for the forge component (with upgraded forge) with no big cost maybe it's worth doing.
>>> 
>>> WDYT?
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/9d1a85de/attachment.html 

From jason at takari.io  Wed Mar 18 22:00:51 2015
From: jason at takari.io (Jason van Zyl)
Date: Wed, 18 Mar 2015 22:00:51 -0400
Subject: [jbosstools-dev] [m2e-dev] Breaking changes to the archetype
	API -> m2e 2.0?
In-Reply-To: <CAG2ouxQ=+X4jq4BfXwG-uUd1braZyNucvdgdvKZ_FZ86g7RTAg@mail.gmail.com>
References: <CAG2ouxQ=+X4jq4BfXwG-uUd1braZyNucvdgdvKZ_FZ86g7RTAg@mail.gmail.com>
Message-ID: <5CAC6B15-6DAF-49D8-B1F4-03361C50ADEE@takari.io>

Is there any downside at all to upgrading? If you've done the work and fixed all those issues I'm super happy you've moved us forward.

Honestly I doubt anyone has tied into the guts of Archetype aside from you and really I think it's a small price to pay if the odd party is. You've updated the code and I assume made it easier to deal with so I only see upside.

+1

On Mar 18, 2015, at 7:45 PM, Fred Bricon <fbricon at gmail.com> wrote:

> Hi,
> 
> I have an initial POC that uses maven-archetype-plugin 2.3, instead of the 2.0.alpha4 version (which was released in the 17th century, give or take).
> 
> I checked it fixes the following issues :
> - https://bugs.eclipse.org/459453, 
> - https://bugs.eclipse.org/424010,
> - https://bugs.eclipse.org/394918, 
> - https://bugs.eclipse.org/374660, 
> - https://bugs.eclipse.org/405945 (on OSX at least), 
> - https://bugs.eclipse.org/415114, 
> - https://bugs.eclipse.org/429287
> 
> Bugs https://bugs.eclipse.org/446657, https://bugs.eclipse.org/348893 may or not be fixed (I can't test proxies)
> 
> Most of these issues were automatically closed already after 1 year of inactivity. Doesn't mean the bugs are not there. My level of annoyance just reached a point where I'd like to take action now.
> 
> The only problem with the archetype update is it will break 3rd party adopters (JBoss Tools at least) depending on the archetype API (package/class names changed between 2.0.alpha4 and 2.3). I don't plan on introducing a compatibility layer, not worth the hassle IMHO.
> Given that I'm also in charge of the JBoss Tools integration, I'm fine with the impact :-)
> 
> Getting the fix in will require m2e to bump its version to 2.0 (and open a bunch of CQs  in ipzilla)
> 
> I'd really like to get that change in for Eclipse Mars, if possible. Is it too late from a release plan standpoint (i.e. 1.6 -> 2.0)? PMC, fellow m2e committers wdyt?
> 
> Fred
> 
> -- 
> "Have you tried turning it off and on again" - The IT Crowd
> _______________________________________________
> m2e-dev mailing list
> m2e-dev at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-dev

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------

First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.

  -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)














From gregory.amerson at liferay.com  Wed Mar 18 23:02:25 2015
From: gregory.amerson at liferay.com (Greg Amerson)
Date: Thu, 19 Mar 2015 11:02:25 +0800
Subject: [jbosstools-dev] [m2e-dev] Breaking changes to the archetype
	API -> m2e 2.0?
In-Reply-To: <5CAC6B15-6DAF-49D8-B1F4-03361C50ADEE@takari.io>
References: <CAG2ouxQ=+X4jq4BfXwG-uUd1braZyNucvdgdvKZ_FZ86g7RTAg@mail.gmail.com>
	<5CAC6B15-6DAF-49D8-B1F4-03361C50ADEE@takari.io>
Message-ID: <CANwu30di61Laq1Ocee34BYDuJe0VoHC3DFdcEjzwefUfh1+K7Q@mail.gmail.com>

Hey Fred,

Just want to clarify some of the APIs that may be changing.  In our adopter
product we have code that looks like this:

final ArchetypeManager archetypeManager =
MavenPluginActivator.getDefault().getArchetypeManager();
final ArtifactRepository remoteArchetypeRepository =
archetypeManager.getArchetypeRepository( archetype );
...
final List<IProject> newProjects =
            projectConfigurationManager.createArchetypeProjects(
                location, archetype, groupId, artifactId, version,
javaPackage, properties, configuration, monitor );


I'm assuming you mean some of these APIs will change in incompatible ways
in the proposed m2e 2.0?  Well I guess ArchetypeManager was always marked
internal, so its fair game to be changed even if m2e doesn't go to 2.0. But
the IProjectConfigurationManager was "API", so is that one of the
interfaces that will undergo breaking change in 2.0?

On Thu, Mar 19, 2015 at 10:00 AM, Jason van Zyl <jason at takari.io> wrote:

> Is there any downside at all to upgrading? If you've done the work and
> fixed all those issues I'm super happy you've moved us forward.
>
> Honestly I doubt anyone has tied into the guts of Archetype aside from you
> and really I think it's a small price to pay if the odd party is. You've
> updated the code and I assume made it easier to deal with so I only see
> upside.
>
> +1
>
> On Mar 18, 2015, at 7:45 PM, Fred Bricon <fbricon at gmail.com> wrote:
>
> > Hi,
> >
> > I have an initial POC that uses maven-archetype-plugin 2.3, instead of
> the 2.0.alpha4 version (which was released in the 17th century, give or
> take).
> >
> > I checked it fixes the following issues :
> > - https://bugs.eclipse.org/459453,
> > - https://bugs.eclipse.org/424010,
> > - https://bugs.eclipse.org/394918,
> > - https://bugs.eclipse.org/374660,
> > - https://bugs.eclipse.org/405945 (on OSX at least),
> > - https://bugs.eclipse.org/415114,
> > - https://bugs.eclipse.org/429287
> >
> > Bugs https://bugs.eclipse.org/446657, https://bugs.eclipse.org/348893
> may or not be fixed (I can't test proxies)
> >
> > Most of these issues were automatically closed already after 1 year of
> inactivity. Doesn't mean the bugs are not there. My level of annoyance just
> reached a point where I'd like to take action now.
> >
> > The only problem with the archetype update is it will break 3rd party
> adopters (JBoss Tools at least) depending on the archetype API
> (package/class names changed between 2.0.alpha4 and 2.3). I don't plan on
> introducing a compatibility layer, not worth the hassle IMHO.
> > Given that I'm also in charge of the JBoss Tools integration, I'm fine
> with the impact :-)
> >
> > Getting the fix in will require m2e to bump its version to 2.0 (and open
> a bunch of CQs  in ipzilla)
> >
> > I'd really like to get that change in for Eclipse Mars, if possible. Is
> it too late from a release plan standpoint (i.e. 1.6 -> 2.0)? PMC, fellow
> m2e committers wdyt?
> >
> > Fred
> >
> > --
> > "Have you tried turning it off and on again" - The IT Crowd
> > _______________________________________________
> > m2e-dev mailing list
> > m2e-dev at eclipse.org
> > To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> First, the taking in of scattered particulars under one Idea,
> so that everyone understands what is being talked about ... Second,
> the separation of the Idea into parts, by dividing it at the joints,
> as nature directs, not breaking any limb in half as a bad carver might.
>
>   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>



-- 
Greg Amerson
Liferay Developer Tools
Liferay, Inc. www.liferay.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150319/fcbb1250/attachment.html 

From fbricon at gmail.com  Wed Mar 18 23:39:21 2015
From: fbricon at gmail.com (Fred Bricon)
Date: Wed, 18 Mar 2015 23:39:21 -0400
Subject: [jbosstools-dev] [m2e-wtp-dev] [m2e-dev] Breaking changes to
 the archetype API -> m2e 2.0?
In-Reply-To: <CANwu30di61Laq1Ocee34BYDuJe0VoHC3DFdcEjzwefUfh1+K7Q@mail.gmail.com>
References: <CAG2ouxQ=+X4jq4BfXwG-uUd1braZyNucvdgdvKZ_FZ86g7RTAg@mail.gmail.com>
	<5CAC6B15-6DAF-49D8-B1F4-03361C50ADEE@takari.io>
	<CANwu30di61Laq1Ocee34BYDuJe0VoHC3DFdcEjzwefUfh1+K7Q@mail.gmail.com>
Message-ID: <CAG2ouxTPpDiMP7yeu-YjHf4Ni3E0SZKaWPBCzBJ5MB=TS+tyLA@mail.gmail.com>

Greg,

only internal m2e classes have been modified, but the archetype runtime
doesn't expose the same Maven classes anymore
(org.apache.maven.archetype.Archetype -> ArchetypeManager) so... it might
not even apply for a major version bump after all. that's debatable I guess.

Here's the extent of the changes, so far :
https://github.com/eclipse/m2e-core/compare/master...fbricon:archetyper-2.x?expand=1

If we can keep on with 1.6 with these changes, fine by me :-)

The downside of moving to 2.0 is a lot of m2e extensions would probably
need to be rebuilt if they use version ranges like [1.0, 2.0). That's
impacts definitely more adopters than the handful that depends on the
archetype API.


On Wed, Mar 18, 2015 at 11:02 PM, Greg Amerson <gregory.amerson at liferay.com>
wrote:

> Hey Fred,
>
> Just want to clarify some of the APIs that may be changing.  In our
> adopter product we have code that looks like this:
>
> final ArchetypeManager archetypeManager =
> MavenPluginActivator.getDefault().getArchetypeManager();
> final ArtifactRepository remoteArchetypeRepository =
> archetypeManager.getArchetypeRepository( archetype );
> ...
> final List<IProject> newProjects =
>             projectConfigurationManager.createArchetypeProjects(
>                 location, archetype, groupId, artifactId, version,
> javaPackage, properties, configuration, monitor );
>
>
> I'm assuming you mean some of these APIs will change in incompatible ways
> in the proposed m2e 2.0?  Well I guess ArchetypeManager was always marked
> internal, so its fair game to be changed even if m2e doesn't go to 2.0. But
> the IProjectConfigurationManager was "API", so is that one of the
> interfaces that will undergo breaking change in 2.0?
>
> On Thu, Mar 19, 2015 at 10:00 AM, Jason van Zyl <jason at takari.io> wrote:
>
>> Is there any downside at all to upgrading? If you've done the work and
>> fixed all those issues I'm super happy you've moved us forward.
>>
>> Honestly I doubt anyone has tied into the guts of Archetype aside from
>> you and really I think it's a small price to pay if the odd party is.
>> You've updated the code and I assume made it easier to deal with so I only
>> see upside.
>>
>> +1
>>
>> On Mar 18, 2015, at 7:45 PM, Fred Bricon <fbricon at gmail.com> wrote:
>>
>> > Hi,
>> >
>> > I have an initial POC that uses maven-archetype-plugin 2.3, instead of
>> the 2.0.alpha4 version (which was released in the 17th century, give or
>> take).
>> >
>> > I checked it fixes the following issues :
>> > - https://bugs.eclipse.org/459453,
>> > - https://bugs.eclipse.org/424010,
>> > - https://bugs.eclipse.org/394918,
>> > - https://bugs.eclipse.org/374660,
>> > - https://bugs.eclipse.org/405945 (on OSX at least),
>> > - https://bugs.eclipse.org/415114,
>> > - https://bugs.eclipse.org/429287
>> >
>> > Bugs https://bugs.eclipse.org/446657, https://bugs.eclipse.org/348893
>> may or not be fixed (I can't test proxies)
>> >
>> > Most of these issues were automatically closed already after 1 year of
>> inactivity. Doesn't mean the bugs are not there. My level of annoyance just
>> reached a point where I'd like to take action now.
>> >
>> > The only problem with the archetype update is it will break 3rd party
>> adopters (JBoss Tools at least) depending on the archetype API
>> (package/class names changed between 2.0.alpha4 and 2.3). I don't plan on
>> introducing a compatibility layer, not worth the hassle IMHO.
>> > Given that I'm also in charge of the JBoss Tools integration, I'm fine
>> with the impact :-)
>> >
>> > Getting the fix in will require m2e to bump its version to 2.0 (and
>> open a bunch of CQs  in ipzilla)
>> >
>> > I'd really like to get that change in for Eclipse Mars, if possible. Is
>> it too late from a release plan standpoint (i.e. 1.6 -> 2.0)? PMC, fellow
>> m2e committers wdyt?
>> >
>> > Fred
>> >
>> > --
>> > "Have you tried turning it off and on again" - The IT Crowd
>> > _______________________________________________
>> > m2e-dev mailing list
>> > m2e-dev at eclipse.org
>> > To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> > https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>> First, the taking in of scattered particulars under one Idea,
>> so that everyone understands what is being talked about ... Second,
>> the separation of the Idea into parts, by dividing it at the joints,
>> as nature directs, not breaking any limb in half as a bad carver might.
>>
>>   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> m2e-dev mailing list
>> m2e-dev at eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>
>
>
>
> --
> Greg Amerson
> Liferay Developer Tools
> Liferay, Inc. www.liferay.com
>
> _______________________________________________
> m2e-wtp-dev mailing list
> m2e-wtp-dev at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
>



-- 
"Have you tried turning it off and on again" - The IT Crowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150318/bb77dd10/attachment-0001.html 

From gregory.amerson at liferay.com  Thu Mar 19 01:29:24 2015
From: gregory.amerson at liferay.com (Greg Amerson)
Date: Thu, 19 Mar 2015 13:29:24 +0800
Subject: [jbosstools-dev] [m2e-wtp-dev] [m2e-dev] Breaking changes to
 the archetype API -> m2e 2.0?
In-Reply-To: <CAG2ouxTPpDiMP7yeu-YjHf4Ni3E0SZKaWPBCzBJ5MB=TS+tyLA@mail.gmail.com>
References: <CAG2ouxQ=+X4jq4BfXwG-uUd1braZyNucvdgdvKZ_FZ86g7RTAg@mail.gmail.com>
	<5CAC6B15-6DAF-49D8-B1F4-03361C50ADEE@takari.io>
	<CANwu30di61Laq1Ocee34BYDuJe0VoHC3DFdcEjzwefUfh1+K7Q@mail.gmail.com>
	<CAG2ouxTPpDiMP7yeu-YjHf4Ni3E0SZKaWPBCzBJ5MB=TS+tyLA@mail.gmail.com>
Message-ID: <CANwu30c+diLgDeAtBhE2-1g4XqGvB4zo+RQK5759CB1O72eJgA@mail.gmail.com>

Thanks for the details Fred.  This change doesn't break our API usage
because we just depend on some m2e-core internal APIs which don't appear to
change with that changeset.

Speaking of which, looking at just this one commit:
https://github.com/fbricon/m2e-core/commit/29e014e49fb2cb442ed2f935590ad1c296a2dfe2

For org.eclipse.m2e.core API I don't see any non-internal API changes, thus
there is no reason here to necessitate a 1.6->2.0 jump.  That leaves the
jars that are bundled in the maven runtime will change with the new
archetyper 2.3 version.  So I guess that is where the 1.6->2.0 major
version bump is required right?

On Thu, Mar 19, 2015 at 11:39 AM, Fred Bricon <fbricon at gmail.com> wrote:

> Greg,
>
> only internal m2e classes have been modified, but the archetype runtime
> doesn't expose the same Maven classes anymore
> (org.apache.maven.archetype.Archetype -> ArchetypeManager) so... it might
> not even apply for a major version bump after all. that's debatable I guess.
>
> Here's the extent of the changes, so far :
> https://github.com/eclipse/m2e-core/compare/master...fbricon:archetyper-2.x?expand=1
>
> If we can keep on with 1.6 with these changes, fine by me :-)
>
> The downside of moving to 2.0 is a lot of m2e extensions would probably
> need to be rebuilt if they use version ranges like [1.0, 2.0). That's
> impacts definitely more adopters than the handful that depends on the
> archetype API.
>
>
> On Wed, Mar 18, 2015 at 11:02 PM, Greg Amerson <
> gregory.amerson at liferay.com> wrote:
>
>> Hey Fred,
>>
>> Just want to clarify some of the APIs that may be changing.  In our
>> adopter product we have code that looks like this:
>>
>> final ArchetypeManager archetypeManager =
>> MavenPluginActivator.getDefault().getArchetypeManager();
>> final ArtifactRepository remoteArchetypeRepository =
>> archetypeManager.getArchetypeRepository( archetype );
>> ...
>> final List<IProject> newProjects =
>>             projectConfigurationManager.createArchetypeProjects(
>>                 location, archetype, groupId, artifactId, version,
>> javaPackage, properties, configuration, monitor );
>>
>>
>> I'm assuming you mean some of these APIs will change in incompatible ways
>> in the proposed m2e 2.0?  Well I guess ArchetypeManager was always marked
>> internal, so its fair game to be changed even if m2e doesn't go to 2.0. But
>> the IProjectConfigurationManager was "API", so is that one of the
>> interfaces that will undergo breaking change in 2.0?
>>
>> On Thu, Mar 19, 2015 at 10:00 AM, Jason van Zyl <jason at takari.io> wrote:
>>
>>> Is there any downside at all to upgrading? If you've done the work and
>>> fixed all those issues I'm super happy you've moved us forward.
>>>
>>> Honestly I doubt anyone has tied into the guts of Archetype aside from
>>> you and really I think it's a small price to pay if the odd party is.
>>> You've updated the code and I assume made it easier to deal with so I only
>>> see upside.
>>>
>>> +1
>>>
>>> On Mar 18, 2015, at 7:45 PM, Fred Bricon <fbricon at gmail.com> wrote:
>>>
>>> > Hi,
>>> >
>>> > I have an initial POC that uses maven-archetype-plugin 2.3, instead of
>>> the 2.0.alpha4 version (which was released in the 17th century, give or
>>> take).
>>> >
>>> > I checked it fixes the following issues :
>>> > - https://bugs.eclipse.org/459453,
>>> > - https://bugs.eclipse.org/424010,
>>> > - https://bugs.eclipse.org/394918,
>>> > - https://bugs.eclipse.org/374660,
>>> > - https://bugs.eclipse.org/405945 (on OSX at least),
>>> > - https://bugs.eclipse.org/415114,
>>> > - https://bugs.eclipse.org/429287
>>> >
>>> > Bugs https://bugs.eclipse.org/446657, https://bugs.eclipse.org/348893
>>> may or not be fixed (I can't test proxies)
>>> >
>>> > Most of these issues were automatically closed already after 1 year of
>>> inactivity. Doesn't mean the bugs are not there. My level of annoyance just
>>> reached a point where I'd like to take action now.
>>> >
>>> > The only problem with the archetype update is it will break 3rd party
>>> adopters (JBoss Tools at least) depending on the archetype API
>>> (package/class names changed between 2.0.alpha4 and 2.3). I don't plan on
>>> introducing a compatibility layer, not worth the hassle IMHO.
>>> > Given that I'm also in charge of the JBoss Tools integration, I'm fine
>>> with the impact :-)
>>> >
>>> > Getting the fix in will require m2e to bump its version to 2.0 (and
>>> open a bunch of CQs  in ipzilla)
>>> >
>>> > I'd really like to get that change in for Eclipse Mars, if possible.
>>> Is it too late from a release plan standpoint (i.e. 1.6 -> 2.0)? PMC,
>>> fellow m2e committers wdyt?
>>> >
>>> > Fred
>>> >
>>> > --
>>> > "Have you tried turning it off and on again" - The IT Crowd
>>> > _______________________________________________
>>> > m2e-dev mailing list
>>> > m2e-dev at eclipse.org
>>> > To change your delivery options, retrieve your password, or
>>> unsubscribe from this list, visit
>>> > https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Takari and Apache Maven
>>> http://twitter.com/jvanzyl
>>> http://twitter.com/takari_io
>>> ---------------------------------------------------------
>>>
>>> First, the taking in of scattered particulars under one Idea,
>>> so that everyone understands what is being talked about ... Second,
>>> the separation of the Idea into parts, by dividing it at the joints,
>>> as nature directs, not breaking any limb in half as a bad carver might.
>>>
>>>   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> m2e-dev mailing list
>>> m2e-dev at eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>
>>
>>
>>
>> --
>> Greg Amerson
>> Liferay Developer Tools
>> Liferay, Inc. www.liferay.com
>>
>> _______________________________________________
>> m2e-wtp-dev mailing list
>> m2e-wtp-dev at eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
>>
>
>
>
> --
> "Have you tried turning it off and on again" - The IT Crowd
>
> _______________________________________________
> m2e-wtp-dev mailing list
> m2e-wtp-dev at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
>



-- 
Greg Amerson
Liferay Developer Tools
Liferay, Inc. www.liferay.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150319/c0b77d4f/attachment.html 

From fbricon at gmail.com  Thu Mar 19 01:41:03 2015
From: fbricon at gmail.com (Fred Bricon)
Date: Thu, 19 Mar 2015 01:41:03 -0400
Subject: [jbosstools-dev] [m2e-wtp-dev] [m2e-dev] Breaking changes to
 the archetype API -> m2e 2.0?
In-Reply-To: <CANwu30c+diLgDeAtBhE2-1g4XqGvB4zo+RQK5759CB1O72eJgA@mail.gmail.com>
References: <CAG2ouxQ=+X4jq4BfXwG-uUd1braZyNucvdgdvKZ_FZ86g7RTAg@mail.gmail.com>
	<5CAC6B15-6DAF-49D8-B1F4-03361C50ADEE@takari.io>
	<CANwu30di61Laq1Ocee34BYDuJe0VoHC3DFdcEjzwefUfh1+K7Q@mail.gmail.com>
	<CAG2ouxTPpDiMP7yeu-YjHf4Ni3E0SZKaWPBCzBJ5MB=TS+tyLA@mail.gmail.com>
	<CANwu30c+diLgDeAtBhE2-1g4XqGvB4zo+RQK5759CB1O72eJgA@mail.gmail.com>
Message-ID: <CAG2ouxSgN+zcgU__ATp_tcnN4+nvjruK9g3QCswQgNndioeJ2w@mail.gmail.com>

Yes, exactly my point. major bump or not, due to archetyper classes
changes, that is the question.

On Thu, Mar 19, 2015 at 1:29 AM, Greg Amerson <gregory.amerson at liferay.com>
wrote:

> Thanks for the details Fred.  This change doesn't break our API usage
> because we just depend on some m2e-core internal APIs which don't appear to
> change with that changeset.
>
> Speaking of which, looking at just this one commit:
> https://github.com/fbricon/m2e-core/commit/29e014e49fb2cb442ed2f935590ad1c296a2dfe2
>
> For org.eclipse.m2e.core API I don't see any non-internal API changes,
> thus there is no reason here to necessitate a 1.6->2.0 jump.  That leaves
> the jars that are bundled in the maven runtime will change with the new
> archetyper 2.3 version.  So I guess that is where the 1.6->2.0 major
> version bump is required right?
>
> On Thu, Mar 19, 2015 at 11:39 AM, Fred Bricon <fbricon at gmail.com> wrote:
>
>> Greg,
>>
>> only internal m2e classes have been modified, but the archetype runtime
>> doesn't expose the same Maven classes anymore
>> (org.apache.maven.archetype.Archetype -> ArchetypeManager) so... it might
>> not even apply for a major version bump after all. that's debatable I guess.
>>
>> Here's the extent of the changes, so far :
>> https://github.com/eclipse/m2e-core/compare/master...fbricon:archetyper-2.x?expand=1
>>
>> If we can keep on with 1.6 with these changes, fine by me :-)
>>
>> The downside of moving to 2.0 is a lot of m2e extensions would probably
>> need to be rebuilt if they use version ranges like [1.0, 2.0). That's
>> impacts definitely more adopters than the handful that depends on the
>> archetype API.
>>
>>
>> On Wed, Mar 18, 2015 at 11:02 PM, Greg Amerson <
>> gregory.amerson at liferay.com> wrote:
>>
>>> Hey Fred,
>>>
>>> Just want to clarify some of the APIs that may be changing.  In our
>>> adopter product we have code that looks like this:
>>>
>>> final ArchetypeManager archetypeManager =
>>> MavenPluginActivator.getDefault().getArchetypeManager();
>>> final ArtifactRepository remoteArchetypeRepository =
>>> archetypeManager.getArchetypeRepository( archetype );
>>> ...
>>> final List<IProject> newProjects =
>>>             projectConfigurationManager.createArchetypeProjects(
>>>                 location, archetype, groupId, artifactId, version,
>>> javaPackage, properties, configuration, monitor );
>>>
>>>
>>> I'm assuming you mean some of these APIs will change in incompatible
>>> ways in the proposed m2e 2.0?  Well I guess ArchetypeManager was always
>>> marked internal, so its fair game to be changed even if m2e doesn't go to
>>> 2.0. But the IProjectConfigurationManager was "API", so is that one of the
>>> interfaces that will undergo breaking change in 2.0?
>>>
>>> On Thu, Mar 19, 2015 at 10:00 AM, Jason van Zyl <jason at takari.io> wrote:
>>>
>>>> Is there any downside at all to upgrading? If you've done the work and
>>>> fixed all those issues I'm super happy you've moved us forward.
>>>>
>>>> Honestly I doubt anyone has tied into the guts of Archetype aside from
>>>> you and really I think it's a small price to pay if the odd party is.
>>>> You've updated the code and I assume made it easier to deal with so I only
>>>> see upside.
>>>>
>>>> +1
>>>>
>>>> On Mar 18, 2015, at 7:45 PM, Fred Bricon <fbricon at gmail.com> wrote:
>>>>
>>>> > Hi,
>>>> >
>>>> > I have an initial POC that uses maven-archetype-plugin 2.3, instead
>>>> of the 2.0.alpha4 version (which was released in the 17th century, give or
>>>> take).
>>>> >
>>>> > I checked it fixes the following issues :
>>>> > - https://bugs.eclipse.org/459453,
>>>> > - https://bugs.eclipse.org/424010,
>>>> > - https://bugs.eclipse.org/394918,
>>>> > - https://bugs.eclipse.org/374660,
>>>> > - https://bugs.eclipse.org/405945 (on OSX at least),
>>>> > - https://bugs.eclipse.org/415114,
>>>> > - https://bugs.eclipse.org/429287
>>>> >
>>>> > Bugs https://bugs.eclipse.org/446657, https://bugs.eclipse.org/348893
>>>> may or not be fixed (I can't test proxies)
>>>> >
>>>> > Most of these issues were automatically closed already after 1 year
>>>> of inactivity. Doesn't mean the bugs are not there. My level of annoyance
>>>> just reached a point where I'd like to take action now.
>>>> >
>>>> > The only problem with the archetype update is it will break 3rd party
>>>> adopters (JBoss Tools at least) depending on the archetype API
>>>> (package/class names changed between 2.0.alpha4 and 2.3). I don't plan on
>>>> introducing a compatibility layer, not worth the hassle IMHO.
>>>> > Given that I'm also in charge of the JBoss Tools integration, I'm
>>>> fine with the impact :-)
>>>> >
>>>> > Getting the fix in will require m2e to bump its version to 2.0 (and
>>>> open a bunch of CQs  in ipzilla)
>>>> >
>>>> > I'd really like to get that change in for Eclipse Mars, if possible.
>>>> Is it too late from a release plan standpoint (i.e. 1.6 -> 2.0)? PMC,
>>>> fellow m2e committers wdyt?
>>>> >
>>>> > Fred
>>>> >
>>>> > --
>>>> > "Have you tried turning it off and on again" - The IT Crowd
>>>> > _______________________________________________
>>>> > m2e-dev mailing list
>>>> > m2e-dev at eclipse.org
>>>> > To change your delivery options, retrieve your password, or
>>>> unsubscribe from this list, visit
>>>> > https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Takari and Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> http://twitter.com/takari_io
>>>> ---------------------------------------------------------
>>>>
>>>> First, the taking in of scattered particulars under one Idea,
>>>> so that everyone understands what is being talked about ... Second,
>>>> the separation of the Idea into parts, by dividing it at the joints,
>>>> as nature directs, not breaking any limb in half as a bad carver might.
>>>>
>>>>   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> m2e-dev mailing list
>>>> m2e-dev at eclipse.org
>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>> from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Greg Amerson
>>> Liferay Developer Tools
>>> Liferay, Inc. www.liferay.com
>>>
>>> _______________________________________________
>>> m2e-wtp-dev mailing list
>>> m2e-wtp-dev at eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
>>>
>>
>>
>>
>> --
>> "Have you tried turning it off and on again" - The IT Crowd
>>
>> _______________________________________________
>> m2e-wtp-dev mailing list
>> m2e-wtp-dev at eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
>>
>
>
>
> --
> Greg Amerson
> Liferay Developer Tools
> Liferay, Inc. www.liferay.com
>
> _______________________________________________
> m2e-wtp-dev mailing list
> m2e-wtp-dev at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
>



-- 
"Have you tried turning it off and on again" - The IT Crowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150319/17a82698/attachment-0001.html 

From nboldt at redhat.com  Thu Mar 19 09:19:08 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 19 Mar 2015 09:19:08 -0400
Subject: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1,
 do we really need a respin?
In-Reply-To: <669DE092-5613-402E-9BDC-98094796F5CC@redhat.com>
References: <5509BB26.6090309@exadel.com>	<F27225E6-65F4-4640-A633-F7AEDE7C2AB3@redhat.com>	<5509E3AC.1020502@exadel.com>
	<669DE092-5613-402E-9BDC-98094796F5CC@redhat.com>
Message-ID: <550ACCCC.8040203@redhat.com>

So... the plan for JBIDE-19468 is to do one of these:

1. fix it ASAP and get it in front of QE after next Thursday's GA code 
freeze (no change to schedule)

  -- OR --

2. fix it today and postpone CR1 by a couple days (change schedule)

  -- OR --

3. reject the release of CR1 entirely (change schedule by keeping CR1 
internal), fix it ASAP, and simply release GA on schedule

What's the best plan here? I can accommodate any of the above.

On 03/18/2015 08:29 PM, Len DiMaggio wrote:
> The full test cycle will wrap up on the 26th - on schedule.
>
> The pre-can-we-release-the-CR1-build-ASAP testing was scheduled for 2
> days - so we will finish that on March 19.
>
> --Len
>
>
> (Sent from my iPhone)
>
>
>
> On Mar 18, 2015, at 4:44 PM, Alexey Kazakov <akazakov at exadel.com
> <mailto:akazakov at exadel.com>> wrote:
>
>> BTW what is QE status for CR1? I don't see any other issues reported
>> in JIRA. How much time do you need to finish CR1 testing?
>>
>>
>> On 03/18/2015 01:23 PM, Len DiMaggio wrote:
>>> Would we want to pull in the fix and try to release CR1 at be end of
>>> the planned QE test cycle? We've already missed the 18th.
>>>
>>> --Len
>>>
>>>
>>> (Sent from my iPhone)
>>>
>>>
>>>
>>> On Mar 18, 2015, at 1:52 PM, Alexey Kazakov <akazakov at exadel.com
>>> <mailto:akazakov at exadel.com>> wrote:
>>>
>>>> Hi,
>>>>
>>>> We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS
>>>> 8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
>>>> It prevents creating a forge addon. The workaround described in the
>>>> JIRA.
>>>> The issue itself doesn't look like a blocker for JBDS 8.1 to me.
>>>> However, George Gastaldi said that they are going to release a fixed
>>>> Forge 2.15.2 today or tomorrow and *IF* we can do a respin for the
>>>> forge component (with upgraded forge) *with no big cost* maybe it's
>>>> worth doing.
>>>>
>>>> WDYT?
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at 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

From ggastald at redhat.com  Thu Mar 19 09:31:56 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 19 Mar 2015 09:31:56 -0400 (EDT)
Subject: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1,
 do we really need a respin?
In-Reply-To: <550ACCCC.8040203@redhat.com>
References: <5509BB26.6090309@exadel.com>
	<F27225E6-65F4-4640-A633-F7AEDE7C2AB3@redhat.com>
	<5509E3AC.1020502@exadel.com>
	<669DE092-5613-402E-9BDC-98094796F5CC@redhat.com>
	<550ACCCC.8040203@redhat.com>
Message-ID: <1698974112.3425719.1426771916645.JavaMail.zimbra@redhat.com>

Hello all, 

For the record, the Forge team released Forge 2.15.2.Final and I created a PR for the jbosstools-4.2.x branch (waiting to be reviewed): https://github.com/jbosstools/jbosstools-forge/pull/138 

Best Regards,

George Gastaldi

----- Original Message -----
From: "Nick Boldt" <nboldt at redhat.com>
To: "Len DiMaggio" <ldimaggi at redhat.com>, "Alexey Kazakov" <akazakov at exadel.com>
Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
Sent: Thursday, March 19, 2015 10:19:08 AM
Subject: Re: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1, do we really need a respin?

So... the plan for JBIDE-19468 is to do one of these:

1. fix it ASAP and get it in front of QE after next Thursday's GA code 
freeze (no change to schedule)

  -- OR --

2. fix it today and postpone CR1 by a couple days (change schedule)

  -- OR --

3. reject the release of CR1 entirely (change schedule by keeping CR1 
internal), fix it ASAP, and simply release GA on schedule

What's the best plan here? I can accommodate any of the above.

On 03/18/2015 08:29 PM, Len DiMaggio wrote:
> The full test cycle will wrap up on the 26th - on schedule.
>
> The pre-can-we-release-the-CR1-build-ASAP testing was scheduled for 2
> days - so we will finish that on March 19.
>
> --Len
>
>
> (Sent from my iPhone)
>
>
>
> On Mar 18, 2015, at 4:44 PM, Alexey Kazakov <akazakov at exadel.com
> <mailto:akazakov at exadel.com>> wrote:
>
>> BTW what is QE status for CR1? I don't see any other issues reported
>> in JIRA. How much time do you need to finish CR1 testing?
>>
>>
>> On 03/18/2015 01:23 PM, Len DiMaggio wrote:
>>> Would we want to pull in the fix and try to release CR1 at be end of
>>> the planned QE test cycle? We've already missed the 18th.
>>>
>>> --Len
>>>
>>>
>>> (Sent from my iPhone)
>>>
>>>
>>>
>>> On Mar 18, 2015, at 1:52 PM, Alexey Kazakov <akazakov at exadel.com
>>> <mailto:akazakov at exadel.com>> wrote:
>>>
>>>> Hi,
>>>>
>>>> We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS
>>>> 8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
>>>> It prevents creating a forge addon. The workaround described in the
>>>> JIRA.
>>>> The issue itself doesn't look like a blocker for JBDS 8.1 to me.
>>>> However, George Gastaldi said that they are going to release a fixed
>>>> Forge 2.15.2 today or tomorrow and *IF* we can do a respin for the
>>>> forge component (with upgraded forge) *with no big cost* maybe it's
>>>> worth doing.
>>>>
>>>> WDYT?
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at 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 at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev

From akazakov at exadel.com  Thu Mar 19 10:03:40 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 19 Mar 2015 07:03:40 -0700
Subject: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1,
 do we really need a respin?
In-Reply-To: <550ACCCC.8040203@redhat.com>
References: <5509BB26.6090309@exadel.com>	<F27225E6-65F4-4640-A633-F7AEDE7C2AB3@redhat.com>	<5509E3AC.1020502@exadel.com>
	<669DE092-5613-402E-9BDC-98094796F5CC@redhat.com>
	<550ACCCC.8040203@redhat.com>
Message-ID: <550AD73C.1080702@exadel.com>

We go with #1.
We release CR1 today with the current/"broken" forge. Fix/upgrade Forge 
in 4.2.x. Include the updated forge component in the upcoming GA release.

On 03/19/2015 06:19 AM, Nick Boldt wrote:
> So... the plan for JBIDE-19468 is to do one of these:
>
> 1. fix it ASAP and get it in front of QE after next Thursday's GA code 
> freeze (no change to schedule)
>
>  -- OR --
>
> 2. fix it today and postpone CR1 by a couple days (change schedule)
>
>  -- OR --
>
> 3. reject the release of CR1 entirely (change schedule by keeping CR1 
> internal), fix it ASAP, and simply release GA on schedule
>
> What's the best plan here? I can accommodate any of the above.
>
> On 03/18/2015 08:29 PM, Len DiMaggio wrote:
>> The full test cycle will wrap up on the 26th - on schedule.
>>
>> The pre-can-we-release-the-CR1-build-ASAP testing was scheduled for 2
>> days - so we will finish that on March 19.
>>
>> --Len
>>
>>
>> (Sent from my iPhone)
>>
>>
>>
>> On Mar 18, 2015, at 4:44 PM, Alexey Kazakov <akazakov at exadel.com
>> <mailto:akazakov at exadel.com>> wrote:
>>
>>> BTW what is QE status for CR1? I don't see any other issues reported
>>> in JIRA. How much time do you need to finish CR1 testing?
>>>
>>>
>>> On 03/18/2015 01:23 PM, Len DiMaggio wrote:
>>>> Would we want to pull in the fix and try to release CR1 at be end of
>>>> the planned QE test cycle? We've already missed the 18th.
>>>>
>>>> --Len
>>>>
>>>>
>>>> (Sent from my iPhone)
>>>>
>>>>
>>>>
>>>> On Mar 18, 2015, at 1:52 PM, Alexey Kazakov <akazakov at exadel.com
>>>> <mailto:akazakov at exadel.com>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS
>>>>> 8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
>>>>> It prevents creating a forge addon. The workaround described in the
>>>>> JIRA.
>>>>> The issue itself doesn't look like a blocker for JBDS 8.1 to me.
>>>>> However, George Gastaldi said that they are going to release a fixed
>>>>> Forge 2.15.2 today or tomorrow and *IF* we can do a respin for the
>>>>> forge component (with upgraded forge) *with no big cost* maybe it's
>>>>> worth doing.
>>>>>
>>>>> WDYT?
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org 
>>>>> <mailto:jbosstools-dev at lists.jboss.org>
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>


From fbricon at redhat.com  Thu Mar 19 10:20:43 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Thu, 19 Mar 2015 10:20:43 -0400
Subject: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1,
	do we really need a respin?
In-Reply-To: <1698974112.3425719.1426771916645.JavaMail.zimbra@redhat.com>
References: <5509BB26.6090309@exadel.com>
	<F27225E6-65F4-4640-A633-F7AEDE7C2AB3@redhat.com>
	<5509E3AC.1020502@exadel.com>
	<669DE092-5613-402E-9BDC-98094796F5CC@redhat.com>
	<550ACCCC.8040203@redhat.com>
	<1698974112.3425719.1426771916645.JavaMail.zimbra@redhat.com>
Message-ID: <015F0553-B2EA-4E86-A30A-14103D60AF68@redhat.com>

It was agreed during today?s PM call this change could go in 8.1.0.GA. I +1'ed the PR

> Le 19 mars 2015 ? 09:31, George Gastaldi <ggastald at redhat.com> a ?crit :
> 
> Hello all, 
> 
> For the record, the Forge team released Forge 2.15.2.Final and I created a PR for the jbosstools-4.2.x branch (waiting to be reviewed): https://github.com/jbosstools/jbosstools-forge/pull/138 
> 
> Best Regards,
> 
> George Gastaldi
> 
> ----- Original Message -----
> From: "Nick Boldt" <nboldt at redhat.com>
> To: "Len DiMaggio" <ldimaggi at redhat.com>, "Alexey Kazakov" <akazakov at exadel.com>
> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
> Sent: Thursday, March 19, 2015 10:19:08 AM
> Subject: Re: [jbosstools-dev] Bug in Forge/JBDS 8.1.0.CR1, do we really need a respin?
> 
> So... the plan for JBIDE-19468 is to do one of these:
> 
> 1. fix it ASAP and get it in front of QE after next Thursday's GA code 
> freeze (no change to schedule)
> 
>  -- OR --
> 
> 2. fix it today and postpone CR1 by a couple days (change schedule)
> 
>  -- OR --
> 
> 3. reject the release of CR1 entirely (change schedule by keeping CR1 
> internal), fix it ASAP, and simply release GA on schedule
> 
> What's the best plan here? I can accommodate any of the above.
> 
> On 03/18/2015 08:29 PM, Len DiMaggio wrote:
>> The full test cycle will wrap up on the 26th - on schedule.
>> 
>> The pre-can-we-release-the-CR1-build-ASAP testing was scheduled for 2
>> days - so we will finish that on March 19.
>> 
>> --Len
>> 
>> 
>> (Sent from my iPhone)
>> 
>> 
>> 
>> On Mar 18, 2015, at 4:44 PM, Alexey Kazakov <akazakov at exadel.com
>> <mailto:akazakov at exadel.com>> wrote:
>> 
>>> BTW what is QE status for CR1? I don't see any other issues reported
>>> in JIRA. How much time do you need to finish CR1 testing?
>>> 
>>> 
>>> On 03/18/2015 01:23 PM, Len DiMaggio wrote:
>>>> Would we want to pull in the fix and try to release CR1 at be end of
>>>> the planned QE test cycle? We've already missed the 18th.
>>>> 
>>>> --Len
>>>> 
>>>> 
>>>> (Sent from my iPhone)
>>>> 
>>>> 
>>>> 
>>>> On Mar 18, 2015, at 1:52 PM, Alexey Kazakov <akazakov at exadel.com
>>>> <mailto:akazakov at exadel.com>> wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS
>>>>> 8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
>>>>> It prevents creating a forge addon. The workaround described in the
>>>>> JIRA.
>>>>> The issue itself doesn't look like a blocker for JBDS 8.1 to me.
>>>>> However, George Gastaldi said that they are going to release a fixed
>>>>> Forge 2.15.2 today or tomorrow and *IF* we can do a respin for the
>>>>> forge component (with upgraded forge) *with no big cost* maybe it's
>>>>> worth doing.
>>>>> 
>>>>> WDYT?
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>> 
>> 
>> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev



From nboldt at redhat.com  Thu Mar 19 14:11:03 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Thu, 19 Mar 2015 14:11:03 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.CR1 ]
Message-ID: <550B1137.4090800@redhat.com>

Component leads, please tag your repositories!

(Note: if you changed nothing in this milestone, you don't have to tag. 
Looking at you, Portlet & Freemarker.)

$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
jbosstools, also often called origin
$ git tag jbosstools-4.2.3.CR1 FETCH_HEAD
$ git push jbosstools jbosstools-4.2.3.CR1

Then, once tagged, *IF YOU CONTRIBUTED FIXES IN Beta1 or CR1 ONLY* 
please bump your root pom to use the latest parent pom, 
4.2.3.Final-SNAPSHOT.

I will send out the usual Task JIRA nags, too.

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From fbricon at redhat.com  Thu Mar 19 14:19:11 2015
From: fbricon at redhat.com (Fred Bricon)
Date: Thu, 19 Mar 2015 14:19:11 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
	please tag your projects [ branch jbosstools-4.2.x -> tag
	jbosstools-4.2.3.CR1 ]
In-Reply-To: <550B1137.4090800@redhat.com>
References: <550B1137.4090800@redhat.com>
Message-ID: <1D2B7363-091C-4014-B44C-5BD100CAA781@redhat.com>

Done for central

> Le 19 mars 2015 ? 14:11, Nick Boldt <nboldt at redhat.com> a ?crit :
> 
> 4.2.3.Final-SNAPSHOT

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150319/338ac17e/attachment.html 

From ggastald at redhat.com  Thu Mar 19 15:10:32 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 19 Mar 2015 16:10:32 -0300
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.CR1 ]
In-Reply-To: <550B1137.4090800@redhat.com>
References: <550B1137.4090800@redhat.com>
Message-ID: <550B1F28.9070608@redhat.com>

Done for forge.

On 03/19/2015 03:11 PM, Nick Boldt wrote:
> Component leads, please tag your repositories!
>
> (Note: if you changed nothing in this milestone, you don't have to tag.
> Looking at you, Portlet & Freemarker.)
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.CR1 FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.CR1
>
> Then, once tagged, *IF YOU CONTRIBUTED FIXES IN Beta1 or CR1 ONLY*
> please bump your root pom to use the latest parent pom,
> 4.2.3.Final-SNAPSHOT.
>
> I will send out the usual Task JIRA nags, too.
>


From akazakov at exadel.com  Thu Mar 19 15:17:57 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 19 Mar 2015 12:17:57 -0700
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.CR1 ]
In-Reply-To: <550B1F28.9070608@redhat.com>
References: <550B1137.4090800@redhat.com> <550B1F28.9070608@redhat.com>
Message-ID: <550B20E5.4070103@exadel.com>

The commit with upgraded Forge 2.15.2 was not included in CR1 - 
https://github.com/jbosstools/jbosstools-forge/commit/431cc4839d8d38563e91f97432b460ee2ef0b54a
So, we should tag 4.2.x as CR1 w/o that commit.

On 03/19/2015 12:10 PM, George Gastaldi wrote:
> Done for forge.
>
> On 03/19/2015 03:11 PM, Nick Boldt wrote:
>> Component leads, please tag your repositories!
>>
>> (Note: if you changed nothing in this milestone, you don't have to tag.
>> Looking at you, Portlet & Freemarker.)
>>
>> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
>> jbosstools, also often called origin
>> $ git tag jbosstools-4.2.3.CR1 FETCH_HEAD
>> $ git push jbosstools jbosstools-4.2.3.CR1
>>
>> Then, once tagged, *IF YOU CONTRIBUTED FIXES IN Beta1 or CR1 ONLY*
>> please bump your root pom to use the latest parent pom,
>> 4.2.3.Final-SNAPSHOT.
>>
>> I will send out the usual Task JIRA nags, too.
>>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From ggastald at redhat.com  Thu Mar 19 15:25:55 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 19 Mar 2015 16:25:55 -0300
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.CR1 ]
In-Reply-To: <550B20E5.4070103@exadel.com>
References: <550B1137.4090800@redhat.com> <550B1F28.9070608@redhat.com>
	<550B20E5.4070103@exadel.com>
Message-ID: <550B22C3.6060507@redhat.com>

Fixed, thanks for pointing that out.

On 03/19/2015 04:17 PM, Alexey Kazakov wrote:
> The commit with upgraded Forge 2.15.2 was not included in CR1 -
> https://github.com/jbosstools/jbosstools-forge/commit/431cc4839d8d38563e91f97432b460ee2ef0b54a
> So, we should tag 4.2.x as CR1 w/o that commit.
>
> On 03/19/2015 12:10 PM, George Gastaldi wrote:
>> Done for forge.
>>
>> On 03/19/2015 03:11 PM, Nick Boldt wrote:
>>> Component leads, please tag your repositories!
>>>
>>> (Note: if you changed nothing in this milestone, you don't have to tag.
>>> Looking at you, Portlet & Freemarker.)
>>>
>>> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
>>> jbosstools, also often called origin
>>> $ git tag jbosstools-4.2.3.CR1 FETCH_HEAD
>>> $ git push jbosstools jbosstools-4.2.3.CR1
>>>
>>> Then, once tagged, *IF YOU CONTRIBUTED FIXES IN Beta1 or CR1 ONLY*
>>> please bump your root pom to use the latest parent pom,
>>> 4.2.3.Final-SNAPSHOT.
>>>
>>> I will send out the usual Task JIRA nags, too.
>>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


From akazakov at exadel.com  Thu Mar 19 20:07:34 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Thu, 19 Mar 2015 17:07:34 -0700
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
 please tag your projects [ branch jbosstools-4.2.x -> tag
 jbosstools-4.2.3.CR1 ]
In-Reply-To: <550B1137.4090800@redhat.com>
References: <550B1137.4090800@redhat.com>
Message-ID: <550B64C6.90406@exadel.com>

Done for base, jst, javaee.

On 03/19/2015 11:11 AM, Nick Boldt wrote:
> Component leads, please tag your repositories!
>
> (Note: if you changed nothing in this milestone, you don't have to tag.
> Looking at you, Portlet & Freemarker.)
>
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.CR1 FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.CR1
>
> Then, once tagged, *IF YOU CONTRIBUTED FIXES IN Beta1 or CR1 ONLY*
> please bump your root pom to use the latest parent pom,
> 4.2.3.Final-SNAPSHOT.
>
> I will send out the usual Task JIRA nags, too.
>


From vrubezhny at exadel.com  Thu Mar 19 20:59:39 2015
From: vrubezhny at exadel.com (Victor V. Rubezhny)
Date: Fri, 20 Mar 2015 03:59:39 +0300
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3 (3.6
	SR2)
Message-ID: <550B70FB.1070003@exadel.com>

Hi,

The JSDT Feature Patch is released for WTP 3.6.3 (3.6 SR2). The patch 
brings the fix for Bug 433515 - Eclipse freezes every few minutes 
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515> back into WTP 3.6 
stream.
Feature Patch is released at The Eclipse Web Tools Platform (WTP) 
software repository 
(http://download.eclipse.org/webtools/repository/luna) 
<http://download.eclipse.org/webtools/repository/luna>.



Can we bring it somehow into JBDS 8 stream or at least to make it 
available for installation by the users?

/Victor

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/dfb83fac/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: WTP Patches 3.6.3-P.png
Type: image/png
Size: 90466 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/dfb83fac/attachment-0001.png 

From manderse at redhat.com  Fri Mar 20 03:23:06 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 20 Mar 2015 03:23:06 -0400 (EDT)
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3
	(3.6	SR2)
In-Reply-To: <550B70FB.1070003@exadel.com>
References: <550B70FB.1070003@exadel.com>
Message-ID: <AC73245A-ACFD-4DB9-A41F-941C3CA6CDBE@redhat.com>

...that would have been great if we had a Jira for that *before* we just closed cr1. 

Please open Jira asap with details. 

Have QE seen this happening ?

/max
http://about.me/maxandersen


> On 20 Mar 2015, at 02:00, Victor V. Rubezhny <vrubezhny at exadel.com> wrote:
> 
> Hi, 
> 
> The JSDT Feature Patch is released for WTP 3.6.3 (3.6 SR2). The patch brings the fix for Bug 433515 - Eclipse freezes every few minutes back into WTP 3.6 stream.
> Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository (http://download.eclipse.org/webtools/repository/luna).
> 
> <WTP Patches 3.6.3-P.png>
> 
> Can we bring it somehow into JBDS 8 stream or at least to make it available for installation by the users?
> 
> /Victor
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/8cae28c5/attachment.html 

From akazakov at exadel.com  Fri Mar 20 03:39:39 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Fri, 20 Mar 2015 00:39:39 -0700
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3
	(3.6	SR2)
In-Reply-To: <AC73245A-ACFD-4DB9-A41F-941C3CA6CDBE@redhat.com>
References: <550B70FB.1070003@exadel.com>
	<AC73245A-ACFD-4DB9-A41F-941C3CA6CDBE@redhat.com>
Message-ID: <E7F81B1F-D53F-4299-8358-4C96171884BC@exadel.com>

Victor, the bugzilla from your email says it's fixed only in WTP 3.7. The Bugzilla is not correct or there is another link for 3.6.3?


> On Mar 20, 2015, at 12:23 AM, Max Rydahl Andersen <manderse at redhat.com> wrote:
> 
> ...that would have been great if we had a Jira for that *before* we just closed cr1. 
> 
> Please open Jira asap with details. 
> 
> Have QE seen this happening ?
> 
> /max
> http://about.me/maxandersen
> 
> 
>> On 20 Mar 2015, at 02:00, Victor V. Rubezhny <vrubezhny at exadel.com> wrote:
>> 
>> Hi, 
>> 
>> The JSDT Feature Patch is released for WTP 3.6.3 (3.6 SR2). The patch brings the fix for Bug 433515 - Eclipse freezes every few minutes back into WTP 3.6 stream.
>> Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository (http://download.eclipse.org/webtools/repository/luna).
>> 
>> <WTP Patches 3.6.3-P.png>
>> 
>> Can we bring it somehow into JBDS 8 stream or at least to make it available for installation by the users?
>> 
>> /Victor
>> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/4241e2b6/attachment.html 

From vrubezhny at exadel.com  Fri Mar 20 06:54:50 2015
From: vrubezhny at exadel.com (Victor V. Rubezhny)
Date: Fri, 20 Mar 2015 13:54:50 +0300
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3
 (3.6	SR2)
In-Reply-To: <AC73245A-ACFD-4DB9-A41F-941C3CA6CDBE@redhat.com>
References: <550B70FB.1070003@exadel.com>
	<AC73245A-ACFD-4DB9-A41F-941C3CA6CDBE@redhat.com>
Message-ID: <550BFC7A.2040302@exadel.com>

This happened just this night, so...

I'm not sure QE has seen something like this issue, they aren't testing 
JavaScript too much and not every JavaScript allows to reproduce this issue.

I've created: https://issues.jboss.org/browse/JBDS-3383 - (JBDS-3383) 
Include Feature Patch for WTP 3..6.3 into JBDS 8.1

/Victor


On 03/20/2015 10:23 AM, Max Rydahl Andersen wrote:
> ...that would have been great if we had a Jira for that *before* we 
> just closed cr1.
>
> Please open Jira asap with details.
>
> Have QE seen this happening ?
>
> /max
> http://about.me/maxandersen
>
>
> On 20 Mar 2015, at 02:00, Victor V. Rubezhny <vrubezhny at exadel.com 
> <mailto:vrubezhny at exadel.com>> wrote:
>
>> Hi,
>>
>> The JSDT Feature Patch is released for WTP 3.6.3 (3.6 SR2). The patch 
>> brings the fix for Bug 433515 - Eclipse freezes every few minutes 
>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515> back into WTP 
>> 3.6 stream.
>> Feature Patch is released at The Eclipse Web Tools Platform (WTP) 
>> software repository 
>> (http://download.eclipse.org/webtools/repository/luna) 
>> <http://download.eclipse.org/webtools/repository/luna>.
>>
>> <WTP Patches 3.6.3-P.png>
>>
>> Can we bring it somehow into JBDS 8 stream or at least to make it 
>> available for installation by the users?
>>
>> /Victor
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/b9656fe5/attachment.html 

From vrubezhny at exadel.com  Fri Mar 20 06:54:58 2015
From: vrubezhny at exadel.com (Victor V. Rubezhny)
Date: Fri, 20 Mar 2015 13:54:58 +0300
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3
 (3.6	SR2)
In-Reply-To: <E7F81B1F-D53F-4299-8358-4C96171884BC@exadel.com>
References: <550B70FB.1070003@exadel.com>
	<AC73245A-ACFD-4DB9-A41F-941C3CA6CDBE@redhat.com>
	<E7F81B1F-D53F-4299-8358-4C96171884BC@exadel.com>
Message-ID: <550BFC82.2000108@exadel.com>

Alexey,

Mentioned issue is fixed in WTP 3.7 stream, but still can be reproduced 
in WTP 3.6.3 (3.6 SR2). As WTP 3.6 stream is closed (no more builds 
here), we've made this Feature Path that, once installed by users, fixes 
this issue in WTP 3.6.3.

Details text at the screenshot says: "Bug 
https://bugs.eclipse.org/461160 Backport the fix for 'Bug 433515 - 
Eclipse freezes every few minutes' into Luna SR2" - there is two issues 
mentioned here:

- Bug# 433515 - is for the issue fixed in WTP 3.7
- Bug# 461160 - is due to bring the fix in WTP 3.6, but since 3.6 stream 
was already closed at the time when the fix was made, we've made this 
Feature Patch that allows to users to fix the issue in their WTP 3.6 SR2 
environment.

/Victor


On 03/20/2015 10:39 AM, Alexey Kazakov wrote:
> Victor, the bugzilla from your email says it's fixed only in WTP 3.7. 
> The Bugzilla is not correct or there is another link for 3.6.3?
>
>
> On Mar 20, 2015, at 12:23 AM, Max Rydahl Andersen <manderse at redhat.com 
> <mailto:manderse at redhat.com>> wrote:
>
>> ...that would have been great if we had a Jira for that *before* we 
>> just closed cr1.
>>
>> Please open Jira asap with details.
>>
>> Have QE seen this happening ?
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>> On 20 Mar 2015, at 02:00, Victor V. Rubezhny <vrubezhny at exadel.com 
>> <mailto:vrubezhny at exadel.com>> wrote:
>>
>>> Hi,
>>>
>>> The JSDT Feature Patch is released for WTP 3.6.3 (3.6 SR2). The 
>>> patch brings the fix for Bug 433515 - Eclipse freezes every few 
>>> minutes <https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515> back 
>>> into WTP 3.6 stream.
>>> Feature Patch is released at The Eclipse Web Tools Platform (WTP) 
>>> software repository 
>>> (http://download.eclipse.org/webtools/repository/luna) 
>>> <http://download.eclipse.org/webtools/repository/luna>.
>>>
>>> <WTP Patches 3.6.3-P.png>
>>>
>>> Can we bring it somehow into JBDS 8 stream or at least to make it 
>>> available for installation by the users?
>>>
>>> /Victor
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/f738f170/attachment-0001.html 

From manderse at redhat.com  Fri Mar 20 07:13:58 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 20 Mar 2015 12:13:58 +0100
Subject: [jbosstools-dev] Fwd: [epp-dev] Heads Up and some action requested
 : TCF Terminals Moving to TM
References: <146B1557584B0B4DBD25ABAD45EF70F0DBC23773@ALA-MBA.corp.ad.wrs.com>
Message-ID: <42A2F428-5B40-46D1-BBDC-2AD7D98BBD32@redhat.com>

Hey,

I believe this will end up affecting us too.

Opened jira for this: https://issues.jboss.org/browse/JBDS-3384

For most this is just a repackaging that don't affect code, but for Fuse 
Tooling
which currently rely on org.eclipse.tm.internal.terminal this will 
require changes.


/max
http://about.me/maxandersen
Forwarded message:

> From: Oberhuber, Martin <Martin.Oberhuber at windriver.com>
> To: Eclipse Packaging Project <epp-dev at eclipse.org>
> Subject: Re: [epp-dev] Heads Up and some action requested : TCF 
> Terminals Moving	to TM
> Date: Thu, 19 Mar 2015 15:54:07 +0000
>
> Hi Package Maintainers,
>
> We have been convinced that contributing from TCF under a foreign 
> namespace is not a good idea.
> On the other hand, the deprecated legacy terminal view has already 
> been removed from the simrel:
> http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=d677d5a6ae094bb2d1a7136be9d5b1d84c62740d
>
> This means there is now some action strongly suggested, or packages 
> might fail to build or build against outdated (M5) terminal 
> contributions:
>
> -          jee : Remove legacy terminal.view , optionally add the new 
> tcf.terminals.view - Bug 
> 462087<https://bugs.eclipse.org/bugs/show_bug.cgi?id=462087>
>
> -          reporting : Remove legacy terminal.view , optionally add 
> the new tcf.terminals.view - Bug 
> 462089<https://bugs.eclipse.org/bugs/show_bug.cgi?id=462089>
>
> -          parallel : Optionally add 
> org.eclipse.tcf.te.terminals.feature AND 
> org.eclipse.tcf.te.terminals.rse.feature
>
> -          cpp : Optionally add org.eclipse.tcf.te.terminals.feature 
> AND org.eclipse.tcf.te.terminals.rse.feature
>
> For the must-have changes in jee and reporting, we have created bugs 
> and Gerrit changesets.
> Since I am an epp committer, I think I could apply these for you, but 
> I would like the package maintainer's OK before I do that.
>
> I would strongly recommend also applying the optional changes (adding 
> the TCF Terminals View) such that users can see the new view and 
> provide feedback.
> Without doing this, the Terminal view would be GONE in the respective 
> packages in M6 and only reappear in M7 once the move has been 
> completed.
> I can also apply these changes for you if I get your OK.
>
> Please let me know how you want to proceed, and if there's any 
> questions/concerns !
>
> Thanks,
> Martin
> --
> Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind River
> direct +43.662.457915.85  fax +43.662.457915.6
>
> From: epp-dev-bounces at eclipse.org [mailto:epp-dev-bounces at eclipse.org] 
> On Behalf Of Oberhuber, Martin
> Sent: Monday, March 16, 2015 6:17 PM
> To: EPP Developer Mailing List (epp-dev at eclipse.org)
> Subject: [epp-dev] Heads Up and some action requested : TCF Terminals 
> Moving to TM
>
> Hi Package Maintainers,
>
> You might be aware that based on the original TM Terminal view, the 
> TCF Project has come up with a much enhanced terminal:
> https://marketplace.eclipse.org/content/tcf-terminals
>
> In order to simplify code adoption and contributions, we want to 
> restructure the codebase and re-unite it with the original TM 
> codebase.
> The result will be called "TM Terminal 4.0" but will contain the 
> related TM _and_ TCF code in a single, small git repository.
> Here is the respective restructuring review:
> https://projects.eclipse.org/projects/tools.cdt.tcf/reviews/move-tcf-terminals-code-tm-project
>
> Now unfortunately the review is scheduled to complete by April 1 which 
> is after M6, but we would like to give adopters
> a preview of the new Terminal with M6 in order to get more feedback. 
> Thus here's what we are planning:
>
> -          The TM project will no longer contribute its 
> org.eclipse.tm.terminal.* to the simrel
>
> -          Instead, the TCF project will contribute 
> org.eclpse.tm.terminal.*_4.0 to the simrel (already using the *new* 
> namespace).
>
> This affects the "jee" and "reporting" packages which currently 
> directly use those features:
>
> org.eclipse.epp.packages/packages>grep org.eclipse.tm.terminal 
> */feature.xml
> org.eclipse.epp.package.jee.feature/feature.xml:      <import 
> feature="org.eclipse.tm.terminal"/>
> org.eclipse.epp.package.jee.feature/feature.xml:      <import 
> feature="org.eclipse.tm.terminal.ssh"/>
> org.eclipse.epp.package.jee.feature/feature.xml:      <import 
> feature="org.eclipse.tm.terminal.telnet"/>
> org.eclipse.epp.package.jee.feature/feature.xml:      <import 
> feature="org.eclipse.tm.terminal.view"/>
> org.eclipse.epp.package.reporting.feature/feature.xml:      <import 
> feature="org.eclipse.tm.terminal"/>
> org.eclipse.epp.package.reporting.feature/feature.xml:      <import 
> feature="org.eclipse.tm.terminal.ssh"/>
> org.eclipse.epp.package.reporting.feature/feature.xml:      <import 
> feature="org.eclipse.tm.terminal.telnet"/>
> org.eclipse.epp.package.reporting.feature/feature.xml:      <import 
> feature="org.eclipse.tm.terminal.view"/>
>
> If you do not take any action, you will simply see the new "4.0" 
> version of those features from TCF, giving you the new tabbed terminal 
> view.
> If you want, you can take the following two actions as soon as TCF 
> starts contributing the new namespace:
>
> -          You may REMOVE "org.eclipse.tm.terminal" since that feature 
> is auto-required by "org.eclipse.tm.terminal.view" ; that would allow 
> updating the widget without updating the view in the future.
>
> -          You may ADD "org.eclipse.tm.terminal.local" since that 
> feature gives you the new local terminal (console) prompt
>
> -          You may want to set the minimum version range to 4.0 to 
> ensure you get the new features
>
> -          You may want to review the terminal whether it fits your 
> needs and provide feedback.
>
> Of course other packages are more than welcome to also consume the new 
> Terminal - all relevant docs are in the marketplace entry cited above.
>
> For now this is just a heads up;
> We are planning to add the new "TM Namespace" features to the TCF 
> simrel contribution over the course of the week.
> I will send another notification once the new features are available.
>
> Please let me know of any concerns or questions !
> Or comment directly on the Move Review if you want.
>
>
> Thanks,
> Martin
> --
> Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind River
> direct +43.662.457915.85  fax +43.662.457915.6
>
> _______________________________________________
> epp-dev mailing list
> epp-dev at eclipse.org
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/epp-dev


From manderse at redhat.com  Fri Mar 20 07:16:20 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 20 Mar 2015 12:16:20 +0100
Subject: [jbosstools-dev] Fuse dev mailing list
Message-ID: <17048093-783D-4A77-AE28-B0449C1F62D1@redhat.com>

FYI: last week jbosstools-fuse-dev at lists.jboss.org was created for 
fuse/datamapper related tooling dev work.

subscribe/archives info at 
https://lists.jboss.org/mailman/listinfo/jbosstools-fuse-dev

/max
http://about.me/maxandersen

From manderse at redhat.com  Fri Mar 20 07:17:52 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 20 Mar 2015 12:17:52 +0100
Subject: [jbosstools-dev] Fuse dev mailing list
Message-ID: <9BC558A7-ED57-483B-9D96-5ADBFAA258CE@redhat.com>

FYI: last week jbosstools-fuse-dev at lists.jboss.org was created for 
fuse/datamapper related tooling dev work.

subscribe/archives info at 
https://lists.jboss.org/mailman/listinfo/jbosstools-fuse-dev

/max
http://about.me/maxandersen

From xcoulon at redhat.com  Fri Mar 20 07:42:41 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Fri, 20 Mar 2015 12:42:41 +0100
Subject: [jbosstools-dev] ACTION REQUIRED: Project leads,
	please tag your projects [ branch jbosstools-4.2.x -> tag
	jbosstools-4.2.3.CR1 ]
In-Reply-To: <550B1137.4090800@redhat.com>
References: <550B1137.4090800@redhat.com>
Message-ID: <D2745B65-CC75-4BFB-9423-05341522E29C@redhat.com>

Done for Webservices.

Best regards,
/Xavier



> On 19 Mar 2015, at 19:11, Nick Boldt <nboldt at redhat.com> wrote:
> 
> Component leads, please tag your repositories!
> 
> (Note: if you changed nothing in this milestone, you don't have to tag. 
> Looking at you, Portlet & Freemarker.)
> 
> $ git fetch jbosstools jbosstools-4.2.x #assuming remote is called 
> jbosstools, also often called origin
> $ git tag jbosstools-4.2.3.CR1 FETCH_HEAD
> $ git push jbosstools jbosstools-4.2.3.CR1
> 
> Then, once tagged, *IF YOU CONTRIBUTED FIXES IN Beta1 or CR1 ONLY* 
> please bump your root pom to use the latest parent pom, 
> 4.2.3.Final-SNAPSHOT.
> 
> I will send out the usual Task JIRA nags, too.
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/4ea0746d/attachment.html 

From manderse at redhat.com  Fri Mar 20 07:54:19 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 20 Mar 2015 12:54:19 +0100
Subject: [jbosstools-dev] rename "testing-tools" to "arquillian"
Message-ID: <98D69EBA-E484-48B3-8C42-7EAB2DF03282@redhat.com>

Hi,

when we creatd "testing-tools" component is was to cover what at the 
time was a sea of testing
fwks like arquillian, shrinkwrap, httpunit, jsfunit etc. but over time 
it is now 99% arquillian.

Normally I would have marked testingt-tools as deprecated and name it zz 
testing-tools and add
new "arquillian" component.

but that seems overkill in this case.

If no objections to this I'll do the rename by Tuesday.

Thanks,
/max
http://about.me/maxandersen

From robert.munteanu at gmail.com  Fri Mar 20 08:42:46 2015
From: robert.munteanu at gmail.com (Robert Munteanu)
Date: Fri, 20 Mar 2015 14:42:46 +0200
Subject: [jbosstools-dev] [m2e-dev] [m2e-wtp-dev] Breaking changes to
 the archetype API -> m2e 2.0?
In-Reply-To: <CAG2ouxSgN+zcgU__ATp_tcnN4+nvjruK9g3QCswQgNndioeJ2w@mail.gmail.com>
References: <CAG2ouxQ=+X4jq4BfXwG-uUd1braZyNucvdgdvKZ_FZ86g7RTAg@mail.gmail.com>
	<5CAC6B15-6DAF-49D8-B1F4-03361C50ADEE@takari.io>
	<CANwu30di61Laq1Ocee34BYDuJe0VoHC3DFdcEjzwefUfh1+K7Q@mail.gmail.com>
	<CAG2ouxTPpDiMP7yeu-YjHf4Ni3E0SZKaWPBCzBJ5MB=TS+tyLA@mail.gmail.com>
	<CANwu30c+diLgDeAtBhE2-1g4XqGvB4zo+RQK5759CB1O72eJgA@mail.gmail.com>
	<CAG2ouxSgN+zcgU__ATp_tcnN4+nvjruK9g3QCswQgNndioeJ2w@mail.gmail.com>
Message-ID: <CAC8ULPYt5059KjVBjE_B5_D-iX491mLsKdqnAoL4gnvNZuHYLQ@mail.gmail.com>

Technically speaking, the m2e bundle should've versioned its exports,
so that consumers can import only the packages that they need with the
version ranges that work for them.

In this situation I don't think bumping the bundle version to 2.0 is
worth breaking most (all?) consumers ; everyone will simply adjust the
import range to [1.x.0;3.0.0) and be done with it.

FTR, we're also consuming the archetype manager APIs, but not the ones
that will change.

Robert

On Thu, Mar 19, 2015 at 7:41 AM, Fred Bricon <fbricon at gmail.com> wrote:
> Yes, exactly my point. major bump or not, due to archetyper classes changes,
> that is the question.
>
> On Thu, Mar 19, 2015 at 1:29 AM, Greg Amerson <gregory.amerson at liferay.com>
> wrote:
>>
>> Thanks for the details Fred.  This change doesn't break our API usage
>> because we just depend on some m2e-core internal APIs which don't appear to
>> change with that changeset.
>>
>> Speaking of which, looking at just this one commit:
>> https://github.com/fbricon/m2e-core/commit/29e014e49fb2cb442ed2f935590ad1c296a2dfe2
>>
>> For org.eclipse.m2e.core API I don't see any non-internal API changes,
>> thus there is no reason here to necessitate a 1.6->2.0 jump.  That leaves
>> the jars that are bundled in the maven runtime will change with the new
>> archetyper 2.3 version.  So I guess that is where the 1.6->2.0 major version
>> bump is required right?
>>
>> On Thu, Mar 19, 2015 at 11:39 AM, Fred Bricon <fbricon at gmail.com> wrote:
>>>
>>> Greg,
>>>
>>> only internal m2e classes have been modified, but the archetype runtime
>>> doesn't expose the same Maven classes anymore
>>> (org.apache.maven.archetype.Archetype -> ArchetypeManager) so... it might
>>> not even apply for a major version bump after all. that's debatable I guess.
>>>
>>> Here's the extent of the changes, so far :
>>> https://github.com/eclipse/m2e-core/compare/master...fbricon:archetyper-2.x?expand=1
>>>
>>> If we can keep on with 1.6 with these changes, fine by me :-)
>>>
>>> The downside of moving to 2.0 is a lot of m2e extensions would probably
>>> need to be rebuilt if they use version ranges like [1.0, 2.0). That's
>>> impacts definitely more adopters than the handful that depends on the
>>> archetype API.
>>>
>>>
>>> On Wed, Mar 18, 2015 at 11:02 PM, Greg Amerson
>>> <gregory.amerson at liferay.com> wrote:
>>>>
>>>> Hey Fred,
>>>>
>>>> Just want to clarify some of the APIs that may be changing.  In our
>>>> adopter product we have code that looks like this:
>>>>
>>>> final ArchetypeManager archetypeManager =
>>>> MavenPluginActivator.getDefault().getArchetypeManager();
>>>> final ArtifactRepository remoteArchetypeRepository =
>>>> archetypeManager.getArchetypeRepository( archetype );
>>>> ...
>>>> final List<IProject> newProjects =
>>>>             projectConfigurationManager.createArchetypeProjects(
>>>>                 location, archetype, groupId, artifactId, version,
>>>> javaPackage, properties, configuration, monitor );
>>>>
>>>>
>>>> I'm assuming you mean some of these APIs will change in incompatible
>>>> ways in the proposed m2e 2.0?  Well I guess ArchetypeManager was always
>>>> marked internal, so its fair game to be changed even if m2e doesn't go to
>>>> 2.0. But the IProjectConfigurationManager was "API", so is that one of the
>>>> interfaces that will undergo breaking change in 2.0?
>>>>
>>>> On Thu, Mar 19, 2015 at 10:00 AM, Jason van Zyl <jason at takari.io> wrote:
>>>>>
>>>>> Is there any downside at all to upgrading? If you've done the work and
>>>>> fixed all those issues I'm super happy you've moved us forward.
>>>>>
>>>>> Honestly I doubt anyone has tied into the guts of Archetype aside from
>>>>> you and really I think it's a small price to pay if the odd party is. You've
>>>>> updated the code and I assume made it easier to deal with so I only see
>>>>> upside.
>>>>>
>>>>> +1
>>>>>
>>>>> On Mar 18, 2015, at 7:45 PM, Fred Bricon <fbricon at gmail.com> wrote:
>>>>>
>>>>> > Hi,
>>>>> >
>>>>> > I have an initial POC that uses maven-archetype-plugin 2.3, instead
>>>>> > of the 2.0.alpha4 version (which was released in the 17th century, give or
>>>>> > take).
>>>>> >
>>>>> > I checked it fixes the following issues :
>>>>> > - https://bugs.eclipse.org/459453,
>>>>> > - https://bugs.eclipse.org/424010,
>>>>> > - https://bugs.eclipse.org/394918,
>>>>> > - https://bugs.eclipse.org/374660,
>>>>> > - https://bugs.eclipse.org/405945 (on OSX at least),
>>>>> > - https://bugs.eclipse.org/415114,
>>>>> > - https://bugs.eclipse.org/429287
>>>>> >
>>>>> > Bugs https://bugs.eclipse.org/446657, https://bugs.eclipse.org/348893
>>>>> > may or not be fixed (I can't test proxies)
>>>>> >
>>>>> > Most of these issues were automatically closed already after 1 year
>>>>> > of inactivity. Doesn't mean the bugs are not there. My level of annoyance
>>>>> > just reached a point where I'd like to take action now.
>>>>> >
>>>>> > The only problem with the archetype update is it will break 3rd party
>>>>> > adopters (JBoss Tools at least) depending on the archetype API
>>>>> > (package/class names changed between 2.0.alpha4 and 2.3). I don't plan on
>>>>> > introducing a compatibility layer, not worth the hassle IMHO.
>>>>> > Given that I'm also in charge of the JBoss Tools integration, I'm
>>>>> > fine with the impact :-)
>>>>> >
>>>>> > Getting the fix in will require m2e to bump its version to 2.0 (and
>>>>> > open a bunch of CQs  in ipzilla)
>>>>> >
>>>>> > I'd really like to get that change in for Eclipse Mars, if possible.
>>>>> > Is it too late from a release plan standpoint (i.e. 1.6 -> 2.0)? PMC, fellow
>>>>> > m2e committers wdyt?
>>>>> >
>>>>> > Fred
>>>>> >
>>>>> > --
>>>>> > "Have you tried turning it off and on again" - The IT Crowd
>>>>> > _______________________________________________
>>>>> > m2e-dev mailing list
>>>>> > m2e-dev at eclipse.org
>>>>> > To change your delivery options, retrieve your password, or
>>>>> > unsubscribe from this list, visit
>>>>> > https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder, Takari and Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> http://twitter.com/takari_io
>>>>> ---------------------------------------------------------
>>>>>
>>>>> First, the taking in of scattered particulars under one Idea,
>>>>> so that everyone understands what is being talked about ... Second,
>>>>> the separation of the Idea into parts, by dividing it at the joints,
>>>>> as nature directs, not breaking any limb in half as a bad carver might.
>>>>>
>>>>>   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> m2e-dev mailing list
>>>>> m2e-dev at eclipse.org
>>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>>> from this list, visit
>>>>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Greg Amerson
>>>> Liferay Developer Tools
>>>> Liferay, Inc. www.liferay.com
>>>>
>>>> _______________________________________________
>>>> m2e-wtp-dev mailing list
>>>> m2e-wtp-dev at eclipse.org
>>>> To change your delivery options, retrieve your password, or unsubscribe
>>>> from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
>>>
>>>
>>>
>>>
>>> --
>>> "Have you tried turning it off and on again" - The IT Crowd
>>>
>>> _______________________________________________
>>> m2e-wtp-dev mailing list
>>> m2e-wtp-dev at eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
>>
>>
>>
>>
>> --
>> Greg Amerson
>> Liferay Developer Tools
>> Liferay, Inc. www.liferay.com
>>
>> _______________________________________________
>> m2e-wtp-dev mailing list
>> m2e-wtp-dev at eclipse.org
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
>
>
>
>
> --
> "Have you tried turning it off and on again" - The IT Crowd
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev at eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-dev



-- 
http://robert.muntea.nu/

From mistria at redhat.com  Fri Mar 20 09:21:44 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 20 Mar 2015 14:21:44 +0100
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3
 (3.6 SR2)
In-Reply-To: <550B70FB.1070003@exadel.com>
References: <550B70FB.1070003@exadel.com>
Message-ID: <550C1EE8.7060000@redhat.com>

On 03/20/2015 01:59 AM, Victor V. Rubezhny wrote:
> Hi,
>
> The JSDT Feature Patch is released for WTP 3.6.3 (3.6 SR2). The patch 
> brings the fix for Bug 433515 - Eclipse freezes every few minutes 
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515> back into WTP 
> 3.6 stream.
> Feature Patch is released at The Eclipse Web Tools Platform (WTP) 
> software repository 
> (http://download.eclipse.org/webtools/repository/luna) 
> <http://download.eclipse.org/webtools/repository/luna>.
Too bad it's a feature patch, would have been easier to just have it as 
a regular feature, with higher version.
Does this issue also happen in JBoss Developer Studio 8.1.0?
-- 
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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/ed28f055/attachment.html 

From manderse at redhat.com  Fri Mar 20 09:59:54 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 20 Mar 2015 14:59:54 +0100
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3
 (3.6 SR2)
In-Reply-To: <550BFC7A.2040302@exadel.com>
References: <550B70FB.1070003@exadel.com>
	<AC73245A-ACFD-4DB9-A41F-941C3CA6CDBE@redhat.com>
	<550BFC7A.2040302@exadel.com>
Message-ID: <A551F8AE-C3A9-417E-9980-2A2B7A2980B4@redhat.com>

On 20 Mar 2015, at 11:54, Victor V. Rubezhny wrote:

> This happened just this night, so...

I assume we didn't just start work on this last night ? :)

My point is that if we know of such serious issues we should get jira 
opened for the related fixversion
with link/info about the situation and marked as blocker so everyone 
will see it before we close down a release.

> I'm not sure QE has seen something like this issue, they aren't 
> testing JavaScript too much and not every JavaScript allows to 
> reproduce this issue.

then that need to be fixed too.

> I've created: https://issues.jboss.org/browse/JBDS-3383 - (JBDS-3383) 
> Include Feature Patch for WTP 3..6.3 into JBDS 8.1

Thanks!

/max

> /Victor
>
>
> On 03/20/2015 10:23 AM, Max Rydahl Andersen wrote:
>> ...that would have been great if we had a Jira for that *before* we 
>> just closed cr1.
>>
>> Please open Jira asap with details.
>>
>> Have QE seen this happening ?
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>> On 20 Mar 2015, at 02:00, Victor V. Rubezhny <vrubezhny at exadel.com 
>> <mailto:vrubezhny at exadel.com>> wrote:
>>
>>> Hi,
>>>
>>> The JSDT Feature Patch is released for WTP 3.6.3 (3.6 SR2). The 
>>> patch brings the fix for Bug 433515 - Eclipse freezes every few 
>>> minutes <https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515> back 
>>> into WTP 3.6 stream.
>>> Feature Patch is released at The Eclipse Web Tools Platform (WTP) 
>>> software repository 
>>> (http://download.eclipse.org/webtools/repository/luna) 
>>> <http://download.eclipse.org/webtools/repository/luna>.
>>>
>>> <WTP Patches 3.6.3-P.png>
>>>
>>> Can we bring it somehow into JBDS 8 stream or at least to make it 
>>> available for installation by the users?
>>>
>>> /Victor
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org 
>>> <mailto:jbosstools-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From vrubezhny at exadel.com  Fri Mar 20 12:36:04 2015
From: vrubezhny at exadel.com (Victor V. Rubezhny)
Date: Fri, 20 Mar 2015 19:36:04 +0300
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3
 (3.6 SR2)
In-Reply-To: <550C1EE8.7060000@redhat.com>
References: <550B70FB.1070003@exadel.com> <550C1EE8.7060000@redhat.com>
Message-ID: <550C4C74.3030409@exadel.com>

Yes, people complain on Feature Patches: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160#c32
And I agree in that having a Feature Patch is not the best solution, 
since users cannot get it by using Help->Check for Updates...

But actually we've made 3 service releases already for WTP 3.6 (SR2 == 
3.6.3) and I don't think that the decision to make another release cycle 
is possible.

/Victor

On 03/20/2015 04:21 PM, Mickael Istria wrote:
> On 03/20/2015 01:59 AM, Victor V. Rubezhny wrote:
>> Hi,
>>
>> The JSDT Feature Patch is released for WTP 3.6.3 (3.6 SR2). The patch 
>> brings the fix for Bug 433515 - Eclipse freezes every few minutes 
>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515> back into WTP 
>> 3.6 stream.
>> Feature Patch is released at The Eclipse Web Tools Platform (WTP) 
>> software repository 
>> (http://download.eclipse.org/webtools/repository/luna) 
>> <http://download.eclipse.org/webtools/repository/luna>.
> Too bad it's a feature patch, would have been easier to just have it 
> as a regular feature, with higher version.
> Does this issue also happen in JBoss Developer Studio 8.1.0?
> -- 
> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/b3f3c211/attachment.html 

From vrubezhny at exadel.com  Fri Mar 20 12:41:18 2015
From: vrubezhny at exadel.com (Victor V. Rubezhny)
Date: Fri, 20 Mar 2015 19:41:18 +0300
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3
 (3.6 SR2)
In-Reply-To: <A551F8AE-C3A9-417E-9980-2A2B7A2980B4@redhat.com>
References: <550B70FB.1070003@exadel.com>
	<AC73245A-ACFD-4DB9-A41F-941C3CA6CDBE@redhat.com>
	<550BFC7A.2040302@exadel.com>
	<A551F8AE-C3A9-417E-9980-2A2B7A2980B4@redhat.com>
Message-ID: <550C4DAE.6040407@exadel.com>

On 03/20/2015 04:59 PM, Max Rydahl Andersen wrote:
> On 20 Mar 2015, at 11:54, Victor V. Rubezhny wrote:
>
>> This happened just this night, so...
>
> I assume we didn't just start work on this last night ? :)
>
> My point is that if we know of such serious issues we should get jira 
> opened for the related fixversion
> with link/info about the situation and marked as blocker so everyone 
> will see it before we close down a release.
Sure, my bad
>> I'm not sure QE has seen something like this issue, they aren't 
>> testing JavaScript too much and not every JavaScript allows to 
>> reproduce this issue.
>
> then that need to be fixed too.
We're working on it.
>
>> I've created: https://issues.jboss.org/browse/JBDS-3383 - (JBDS-3383) 
>> Include Feature Patch for WTP 3..6.3 into JBDS 8.1
>
> Thanks!
>
> /max
>
>> /Victor
>>
>>
>> On 03/20/2015 10:23 AM, Max Rydahl Andersen wrote:
>>> ...that would have been great if we had a Jira for that *before* we 
>>> just closed cr1.
>>>
>>> Please open Jira asap with details.
>>>
>>> Have QE seen this happening ?
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>>
>>> On 20 Mar 2015, at 02:00, Victor V. Rubezhny <vrubezhny at exadel.com 
>>> <mailto:vrubezhny at exadel.com>> wrote:
>>>
>>>> Hi,
>>>>
>>>> The JSDT Feature Patch is released for WTP 3.6.3 (3.6 SR2). The 
>>>> patch brings the fix for Bug 433515 - Eclipse freezes every few 
>>>> minutes <https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515> back 
>>>> into WTP 3.6 stream.
>>>> Feature Patch is released at The Eclipse Web Tools Platform (WTP) 
>>>> software repository 
>>>> (http://download.eclipse.org/webtools/repository/luna) 
>>>> <http://download.eclipse.org/webtools/repository/luna>.
>>>>
>>>> <WTP Patches 3.6.3-P.png>
>>>>
>>>> Can we bring it somehow into JBDS 8 stream or at least to make it 
>>>> available for installation by the users?
>>>>
>>>> /Victor
>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen


From mistria at redhat.com  Fri Mar 20 13:50:48 2015
From: mistria at redhat.com (Mickael Istria)
Date: Fri, 20 Mar 2015 18:50:48 +0100
Subject: [jbosstools-dev] JSDT Feature Patch is released for WTP 3.6.3
 (3.6 SR2)
In-Reply-To: <550C4C74.3030409@exadel.com>
References: <550B70FB.1070003@exadel.com> <550C1EE8.7060000@redhat.com>
	<550C4C74.3030409@exadel.com>
Message-ID: <550C5DF8.2030009@redhat.com>

On 03/20/2015 05:36 PM, Victor V. Rubezhny wrote:
> But actually we've made 3 service releases already for WTP 3.6 (SR2 == 
> 3.6.3) and I don't think that the decision to make another release 
> cycle is possible.
Let's use a universal answer there: "Why not?"
-- 
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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150320/ec64c8d2/attachment.html 

From akazakov at exadel.com  Fri Mar 20 15:04:53 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Fri, 20 Mar 2015 12:04:53 -0700
Subject: [jbosstools-dev] JBoss Developer Studio 8.1.0.CR1 is available
Message-ID: <550C6F55.1000705@exadel.com>


JBoss Developer Studio 8.1.0.CR1 is available!

Download page and installer:
* https://tools.jboss.org/downloads/devstudio/luna/8.1.0.CR1.html
* https://www.jboss.org/products/devstudio/overview/

Update site: https://devstudio.jboss.com/updates/8.0-development/

Early Access site: https://devstudio.jboss.com/earlyaccess/8.0-development/

Schedule / Upcoming Releases: 
https://issues.jboss.org/browse/JBDS#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel 


From akazakov at exadel.com  Fri Mar 20 15:05:13 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Fri, 20 Mar 2015 12:05:13 -0700
Subject: [jbosstools-dev] JBoss Tools 4.2.3.CR1 is now available
Message-ID: <550C6F69.5040105@exadel.com>

This is a development release aimed at Eclipse 4.4.2 Luna SR2 users.

Update Site: http://download.jboss.org/jbosstools/updates/development/luna/

Update Site Zips: 
http://sourceforge.net/projects/jboss/files/JBossTools/jbosstools4.2.3.x/

Installation instructions: 
http://tools.jboss.org/downloads/installation.html

New + Noteworthy (subject to change): 
http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.3.CR1.html

Schedule / Upcoming Releases: 
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel 


From nboldt at redhat.com  Fri Mar 20 15:14:48 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 20 Mar 2015 15:14:48 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.3.Final / 8.1.0.GA
Message-ID: <550C71A8.3050307@redhat.com>

== Schedule reminder ==

Code freeze for GA is next Thursday, March 26, which means we'll be 
releasing the JBT/JBDS 4.42.0.Final-SNAPSHOT target platforms no later 
than Wednesday, March 25.

== Changes to TP? ==

If you have anything urgent that needs to be added/changed in the TPs, 
speak up now! (We already know about the WTP 3.6.3 feature patch - see 
JBDS-3383.)

== TODO: use latest parent pom ==

Because this is a .Final, we need to ensure everyone uses the correct 
latest target platform and parent pom, 4.2.3.Final-SNAPSHOT.

Details in the following Task JIRAs:

JBDS              : https://issues.jboss.org/browse/JBDS-3385
JBoss Tools       : https://issues.jboss.org/browse/JBIDE-19480
JBT Update Sites  : https://issues.jboss.org/browse/JBIDE-19481
Central           : https://issues.jboss.org/browse/JBIDE-19482
Hibernate         : https://issues.jboss.org/browse/JBIDE-19483
Webservices       : https://issues.jboss.org/browse/JBIDE-19484
VPE               : https://issues.jboss.org/browse/JBIDE-19485
Forge             : https://issues.jboss.org/browse/JBIDE-19486
Aerogear          : https://issues.jboss.org/browse/JBIDE-19487
Central Discovery : https://issues.jboss.org/browse/JBIDE-19488
JST               : https://issues.jboss.org/browse/JBIDE-19489
Server            : https://issues.jboss.org/browse/JBIDE-19490
Base              : https://issues.jboss.org/browse/JBIDE-19491
BrowserSim        : https://issues.jboss.org/browse/JBIDE-19492
JavaEE            : https://issues.jboss.org/browse/JBIDE-19493


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From mistria at redhat.com  Mon Mar 23 02:31:32 2015
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 23 Mar 2015 07:31:32 +0100
Subject: [jbosstools-dev] Which modules depend on EGit/JGit?
Message-ID: <550FB344.6090404@redhat.com>

Hi all,

With https://issues.jboss.org/browse/JBDS-3285 , we'll most likely need 
to adopt snapshots of EGit/JGit 4.0 in our target-platform for JBT 4.3.
What are the impacted modules? Do you already expect some issues related 
to this move? Are you actively following JGit/EGit changes to react to 
them ASAP?
In short, would it be OK to adopt snapshots from now on?

Cheers,
-- 
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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150323/40988056/attachment.html 

From manderse at redhat.com  Mon Mar 23 03:50:18 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 23 Mar 2015 03:50:18 -0400 (EDT)
Subject: [jbosstools-dev] Which modules depend on EGit/JGit?
In-Reply-To: <550FB344.6090404@redhat.com>
References: <550FB344.6090404@redhat.com>
Message-ID: <F0FD6888-4811-4D3F-A8BB-B690606DD41B@redhat.com>

I'm pretty sure very few if any is actively using latest snapshot. 

Won't this be included in the upcoming M6 so we can get it into the TP?

If not, then make the TP PR for the snapshot and we can run the build to find out if anything breaks ?

Btw. The only two parts I know that uses jgit/egit directly is thym and OpenShift. 

/max
http://about.me/maxandersen


> On 23 Mar 2015, at 07:31, Mickael Istria <mistria at redhat.com> wrote:
> 
> Hi all,
> 
> With https://issues.jboss.org/browse/JBDS-3285 , we'll most likely need to adopt snapshots of EGit/JGit 4.0 in our target-platform for JBT 4.3.
> What are the impacted modules? Do you already expect some issues related to this move? Are you actively following JGit/EGit changes to react to them ASAP?
> In short, would it be OK to adopt snapshots from now on?
> 
> Cheers,
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150323/a507c98a/attachment.html 

From adietish at redhat.com  Mon Mar 23 04:58:32 2015
From: adietish at redhat.com (=?windows-1252?Q?Andr=E9_Dietisheim?=)
Date: Mon, 23 Mar 2015 09:58:32 +0100
Subject: [jbosstools-dev] Which modules depend on EGit/JGit?
In-Reply-To: <F0FD6888-4811-4D3F-A8BB-B690606DD41B@redhat.com>
References: <550FB344.6090404@redhat.com>
	<F0FD6888-4811-4D3F-A8BB-B690606DD41B@redhat.com>
Message-ID: <550FD5B8.50309@redhat.com>

In the OpenShift v2 tooling I am depending on a few internal classes to 
show a customized commit dialog when pushing to OpenShift. Even though 
not ideal there was not obvious better way to achieve that, given that 
EGit is poorly written and very much not with extensibility in mind (the 
plan was to provide a PR though). I thus pretty much expect OpenShift v2 
to break. Could we please provide a smooth transition and give me some 
time to provide the required changes?

Cheers
Andr?

On 03/23/2015 08:50 AM, Max Rydahl Andersen wrote:
> I'm pretty sure very few if any is actively using latest snapshot.
>
> Won't this be included in the upcoming M6 so we can get it into the TP?
>
> If not, then make the TP PR for the snapshot and we can run the build 
> to find out if anything breaks ?
>
> Btw. The only two parts I know that uses jgit/egit directly is thym 
> and OpenShift.
>
> /max
> http://about.me/maxandersen
>
>
> On 23 Mar 2015, at 07:31, Mickael Istria <mistria at redhat.com 
> <mailto:mistria at redhat.com>> wrote:
>
>> Hi all,
>>
>> With https://issues.jboss.org/browse/JBDS-3285 , we'll most likely 
>> need to adopt snapshots of EGit/JGit 4.0 in our target-platform for 
>> JBT 4.3.
>> What are the impacted modules? Do you already expect some issues 
>> related to this move? Are you actively following JGit/EGit changes to 
>> react to them ASAP?
>> In short, would it be OK to adopt snapshots from now on?
>>
>> Cheers,
>> -- 
>> 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 at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150323/1bf511f6/attachment.html 

From mistria at redhat.com  Mon Mar 23 05:15:23 2015
From: mistria at redhat.com (Mickael Istria)
Date: Mon, 23 Mar 2015 10:15:23 +0100
Subject: [jbosstools-dev] Which modules depend on EGit/JGit?
In-Reply-To: <550FD5B8.50309@redhat.com>
References: <550FB344.6090404@redhat.com>
	<F0FD6888-4811-4D3F-A8BB-B690606DD41B@redhat.com>
	<550FD5B8.50309@redhat.com>
Message-ID: <550FD9AB.6000201@redhat.com>

On 03/23/2015 09:58 AM, Andr? Dietisheim wrote:
> In the OpenShift v2 tooling I am depending on a few internal classes 
> to show a customized commit dialog when pushing to OpenShift. Even 
> though not ideal there was not obvious better way to achieve that, 
> given that EGit is poorly written and very much not with extensibility 
> in mind (the plan was to provide a PR though). I thus pretty much 
> expect OpenShift v2 to break. Could we please provide a smooth 
> transition and give me some time to provide the required changes?
For the Easymport wizard, I asked to turn some classes and methods as 
APIs, and Matthias has helped with that. I guess EGit can open APIs on 
request, and for sure, providing Gerrit patches makes it faster. Note 
that since they're moving to a 4.0, it's the right time to 
request/propose API changes.
I got confirmation on the egit-dev mailing-list that Mars M6 will 
include a milestone of EGit 4.0, that will be part of our TP when we 
move to M6.
-- 
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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150323/456e218f/attachment.html 

From manderse at redhat.com  Mon Mar 23 06:26:02 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 23 Mar 2015 11:26:02 +0100
Subject: [jbosstools-dev] welcome to 'docker'
Message-ID: <CAAFE375-A320-45BF-9024-DB6862F44EA7@redhat.com>

Hey,

It's been looming but now it has happened.

For a while 'docker' issues been put under 'openshift' but now that 
docker will be mainly
at eclipse.org (under linux tools) and the persons doing it are 
different we agreed on creating
  a dedicated 'docker' component to make it easier to search/report 
against.

I've created it in both JBIDE and JBDS.

/max
http://about.me/maxandersen

From gorkem.ercan at gmail.com  Mon Mar 23 08:05:02 2015
From: gorkem.ercan at gmail.com (Gorkem Ercan)
Date: Mon, 23 Mar 2015 08:05:02 -0400
Subject: [jbosstools-dev] Which modules depend on EGit/JGit?
In-Reply-To: <550FB344.6090404@redhat.com>
References: <550FB344.6090404@redhat.com>
Message-ID: <8FCD0821-186E-440D-9972-76EAD4B9EBE7@gmail.com>



On 23 Mar 2015, at 2:31, Mickael Istria wrote:

> Hi all,
>
> With https://issues.jboss.org/browse/JBDS-3285 , we'll most likely 
> need to adopt snapshots of EGit/JGit 4.0 in our target-platform for 
> JBT 4.3.
> What are the impacted modules?

jbosstools-aerogear, FeedHenry component uses EGit and JGit. It uses an 
internal API from EGit.
And indirectly Thym uses JGit.

> Do you already expect some issues related to this move?
I have not checked if our public/private API uses impacted on 4.0.

> Are you actively following JGit/EGit changes to react to them ASAP?
No.

> In short, would it be OK to adopt snapshots from now on?
Only if snapshots do not break anything :)
Actually, I am a bit concerned about Thym.
>
> Cheers,
> -- 
> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

From manderse at redhat.com  Mon Mar 23 11:01:42 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 23 Mar 2015 16:01:42 +0100
Subject: [jbosstools-dev] Which modules depend on EGit/JGit?
In-Reply-To: <550FD5B8.50309@redhat.com>
References: <550FB344.6090404@redhat.com>
	<F0FD6888-4811-4D3F-A8BB-B690606DD41B@redhat.com>
	<550FD5B8.50309@redhat.com>
Message-ID: <9311104F-E85F-47C4-921F-AA100C806AE8@redhat.com>

On 23 Mar 2015, at 9:58, Andr? Dietisheim wrote:

> In the OpenShift v2 tooling I am depending on a few internal classes 
> to show a customized commit dialog when pushing to OpenShift. Even 
> though not ideal there was not obvious better way to achieve that, 
> given that EGit is poorly written and very much not with extensibility 
> in mind (the plan was to provide a PR though). I thus pretty much 
> expect OpenShift v2 to break. Could we please provide a smooth 
> transition and give me some time to provide the required changes?

The cut off happens when Eclipse M6 goes out - so thats in 4 days.

How much time do you need ?


/max

>
> Cheers
> Andr?
>
> On 03/23/2015 08:50 AM, Max Rydahl Andersen wrote:
>> I'm pretty sure very few if any is actively using latest snapshot.
>>
>> Won't this be included in the upcoming M6 so we can get it into the 
>> TP?
>>
>> If not, then make the TP PR for the snapshot and we can run the build 
>> to find out if anything breaks ?
>>
>> Btw. The only two parts I know that uses jgit/egit directly is thym 
>> and OpenShift.
>>
>> /max
>> http://about.me/maxandersen
>>
>>
>> On 23 Mar 2015, at 07:31, Mickael Istria <mistria at redhat.com 
>> <mailto:mistria at redhat.com>> wrote:
>>
>>> Hi all,
>>>
>>> With https://issues.jboss.org/browse/JBDS-3285 , we'll most likely 
>>> need to adopt snapshots of EGit/JGit 4.0 in our target-platform for 
>>> JBT 4.3.
>>> What are the impacted modules? Do you already expect some issues 
>>> related to this move? Are you actively following JGit/EGit changes 
>>> to react to them ASAP?
>>> In short, would it be OK to adopt snapshots from now on?
>>>
>>> Cheers,
>>> -- 
>>> 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 at lists.jboss.org 
>>> <mailto:jbosstools-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

From manderse at redhat.com  Mon Mar 23 11:04:23 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Mon, 23 Mar 2015 16:04:23 +0100
Subject: [jbosstools-dev] Which modules depend on EGit/JGit?
In-Reply-To: <8FCD0821-186E-440D-9972-76EAD4B9EBE7@gmail.com>
References: <550FB344.6090404@redhat.com>
	<8FCD0821-186E-440D-9972-76EAD4B9EBE7@gmail.com>
Message-ID: <F8B46C7C-C4C4-41AB-B85B-E9BCF8DA88C1@redhat.com>

On 23 Mar 2015, at 13:05, Gorkem Ercan wrote:

> On 23 Mar 2015, at 2:31, Mickael Istria wrote:
>
>> Hi all,
>>
>> With https://issues.jboss.org/browse/JBDS-3285 , we'll most likely
>> need to adopt snapshots of EGit/JGit 4.0 in our target-platform for
>> JBT 4.3.
>> What are the impacted modules?
>
> jbosstools-aerogear, FeedHenry component uses EGit and JGit. It uses 
> an
> internal API from EGit.
> And indirectly Thym uses JGit.

ah - I forgot about feedhenry/thym combo.

Sounds like both OpenShift and Aerogear should take a look at what 
internal API we use
and at least open bugzilla to request some of this gets upgraded to API 
?
(assuming we still need the features)

>> Do you already expect some issues related to this move?
> I have not checked if our public/private API uses impacted on 4.0.

Can you find time to check that this week or monday ? M6 is set to go 
out
friday and we would like to get the easy import work moving forward.

>> In short, would it be OK to adopt snapshots from now on?
> Only if snapshots do not break anything :)
> Actually, I am a bit concerned about Thym.

sounds like its time to have separate Luna/Mars streams ? :/

/max
http://about.me/maxandersen

From adietish at redhat.com  Mon Mar 23 11:37:21 2015
From: adietish at redhat.com (=?windows-1252?Q?Andr=E9_Dietisheim?=)
Date: Mon, 23 Mar 2015 16:37:21 +0100
Subject: [jbosstools-dev] Which modules depend on EGit/JGit?
In-Reply-To: <550FD9AB.6000201@redhat.com>
References: <550FB344.6090404@redhat.com>
	<F0FD6888-4811-4D3F-A8BB-B690606DD41B@redhat.com>
	<550FD5B8.50309@redhat.com> <550FD9AB.6000201@redhat.com>
Message-ID: <55103331.1060503@redhat.com>



On 03/23/2015 10:15 AM, Mickael Istria wrote:
> On 03/23/2015 09:58 AM, Andr? Dietisheim wrote:
>> In the OpenShift v2 tooling I am depending on a few internal classes 
>> to show a customized commit dialog when pushing to OpenShift. Even 
>> though not ideal there was not obvious better way to achieve that, 
>> given that EGit is poorly written and very much not with 
>> extensibility in mind (the plan was to provide a PR though). I thus 
>> pretty much expect OpenShift v2 to break. Could we please provide a 
>> smooth transition and give me some time to provide the required changes?
> For the Easymport wizard, I asked to turn some classes and methods as 
> APIs, and Matthias has helped with that. 

yes I loosely followed this discussed. Beside that I guess that this is 
not enough for my usage of the commit dialog. It was clearly not 
implemented with extensibility in mind. I'll have to fill PRs for that 
to fit my needs.

> I guess EGit can open APIs on request, and for sure, providing Gerrit 
> patches makes it faster. Note that since they're moving to a 4.0, it's 
> the right time to request/propose API changes.

Yes I think I'll have to do that. On the other hand not sure how much 
time I'll have for that given that we need v3 tooling this june.

> I got confirmation on the egit-dev mailing-list that Mars M6 will 
> include a milestone of EGit 4.0, that will be part of our TP when we 
> move to M6.

Ok let me add latest EGit to my TP and check what changes break me in 
all details.

> -- 
> 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>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150323/17d9266c/attachment.html 

From nboldt at redhat.com  Mon Mar 23 11:37:43 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 23 Mar 2015 11:37:43 -0400
Subject: [jbosstools-dev] Proposal to add WTP 3.6.3 feature patch to
 JBT/JBDS target platforms 4.42.0.Final-SNAPSHOT
Message-ID: <55103347.1060505@redhat.com>

We need to add a single patch feature and its accompanying single plugin 
to the target platform.

https://issues.jboss.org/browse/JBDS-3383
https://github.com/jbosstools/jbosstools-target-platforms/pull/135

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From gorkem.ercan at gmail.com  Mon Mar 23 12:06:44 2015
From: gorkem.ercan at gmail.com (Gorkem Ercan)
Date: Mon, 23 Mar 2015 12:06:44 -0400
Subject: [jbosstools-dev] Which modules depend on EGit/JGit?
In-Reply-To: <F8B46C7C-C4C4-41AB-B85B-E9BCF8DA88C1@redhat.com>
References: <550FB344.6090404@redhat.com>
	<8FCD0821-186E-440D-9972-76EAD4B9EBE7@gmail.com>
	<F8B46C7C-C4C4-41AB-B85B-E9BCF8DA88C1@redhat.com>
Message-ID: <54B67098-B97C-4EC8-AF7D-2D065B1DC437@gmail.com>



On 23 Mar 2015, at 11:04, Max Rydahl Andersen wrote:

> On 23 Mar 2015, at 13:05, Gorkem Ercan wrote:
>
>> On 23 Mar 2015, at 2:31, Mickael Istria wrote:
>>
>>> Hi all,
>>>
>>> With https://issues.jboss.org/browse/JBDS-3285 , we'll most likely
>>> need to adopt snapshots of EGit/JGit 4.0 in our target-platform for
>>> JBT 4.3.
>>> What are the impacted modules?
>>
>> jbosstools-aerogear, FeedHenry component uses EGit and JGit. It uses 
>> an
>> internal API from EGit.
>> And indirectly Thym uses JGit.
>
> ah - I forgot about feedhenry/thym combo.
>
> Sounds like both OpenShift and Aerogear should take a look at what 
> internal API we use
> and at least open bugzilla to request some of this gets upgraded to 
> API ?
> (assuming we still need the features)
>
>>> Do you already expect some issues related to this move?
>> I have not checked if our public/private API uses impacted on 4.0.
>
> Can you find time to check that this week or monday ?

I will try to check tomorrow (Tuesday).

> M6 is set to go out
> friday and we would like to get the easy import work moving forward.
>
>>> In short, would it be OK to adopt snapshots from now on?
>> Only if snapshots do not break anything :)
>> Actually, I am a bit concerned about Thym.
>
> sounds like its time to have separate Luna/Mars streams ? :/

separate streams = https://www.youtube.com/watch?v=73IxEmUsMGY

>
> /max
> http://about.me/maxandersen

From nboldt at redhat.com  Mon Mar 23 16:08:27 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Mon, 23 Mar 2015 16:08:27 -0400
Subject: [jbosstools-dev] Proposal to add WTP 3.6.3 feature patch to
 JBT/JBDS target platforms 4.42.0.Final-SNAPSHOT
In-Reply-To: <55103347.1060505@redhat.com>
References: <55103347.1060505@redhat.com>
Message-ID: <551072BB.9090704@redhat.com>

Here's the p2diff:

  ~/tmp/p2diff/p2diff -mode=ignoreVersions -query=groups -onlylatest 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.42.0.Final-SNAPSHOT/REPO/ 
file:///home/nboldt/42x/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/

 > org.eclipse.wst.jsdt.feature.patch.feature.group [3.6.3.v201503191608]
=== Summary ===
file:///home/nboldt/42x/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ 
contains 1 unique IUs

As the TP needs to be published to Nexus *no later than this Wednesday* 
(Code Freeze for 4.2.3.Final is this Thursday), I've pushed this change 
and it's building now [1], so that it will be easier for everyone to 
use/test. If you feel this is a problem, I can of course back out the 
commit.

[1] 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Target-Platforms/job/jbosstoolstargetplatforms-matrix/ 
 >=382

On 03/23/2015 11:37 AM, Nick Boldt wrote:
> We need to add a single patch feature and its accompanying single plugin
> to the target platform.
>
> https://issues.jboss.org/browse/JBDS-3383
> https://github.com/jbosstools/jbosstools-target-platforms/pull/135
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From manderse at redhat.com  Tue Mar 24 03:00:05 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Tue, 24 Mar 2015 03:00:05 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201503240700.t2O705Pq025898@int-mx13.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-19500

https://issues.jboss.org/browse/JBIDE-19500
Summary: warn/inform users running on non-compatilbe JVMs they are loosing out on features

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 9:13:12.314519

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From mistria at redhat.com  Tue Mar 24 04:58:20 2015
From: mistria at redhat.com (Mickael Istria)
Date: Tue, 24 Mar 2015 09:58:20 +0100
Subject: [jbosstools-dev] Site doesn't mention VPE/VPV,
	JS editor addition nor JSF support?
Message-ID: <5511272C.8020106@redhat.com>

Hi all,

As I'm trying to write an answer on some French forum about how to do 
JSF in Eclipse, I realize I couldn't find a good link to what JBoss 
Tools provide on this topic.
I expected to find at least a paragraph about JSF editor from 
http://tools.jboss.org/features/ but couldn't find one. Have I missed 
it, or are we intentionally hiding our JSF tools from that page?
The same goes for our JavaScript tools and for Visual Preview. I believe 
those are interesting features to highlight and I believe they lack 
visibility from the website.

Should I open a Jira for that?
-- 
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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/58056bf6/attachment.html 

From ibuziuk at exadel.com  Tue Mar 24 05:17:49 2015
From: ibuziuk at exadel.com (Ilya Buziuk)
Date: Tue, 24 Mar 2015 12:17:49 +0300
Subject: [jbosstools-dev] Site doesn't mention VPE/VPV,
 JS editor addition nor JSF support?
In-Reply-To: <5511272C.8020106@redhat.com>
References: <5511272C.8020106@redhat.com>
Message-ID: <CADOkA46yWG4GMkYp6vPSqB8NONj2V8=rW=WQ9FFyKxeFnswvjA@mail.gmail.com>

< I expected to find at least a paragraph about JSF editor from
http://tools.jboss.org/features/ but couldn't find one
It's utterly surprising that our users are interested in JSF
stuff while when we are deprecating Xulrunner ;-)

< The same goes for our JavaScript tools and for Visual Preview. I believe
those are interesting features to highlight and I believe they lack
visibility from the website.
Agreed about that. I can provide a PR to the site about HTML Preview
feature.

On Tue, Mar 24, 2015 at 11:58 AM, Mickael Istria <mistria at redhat.com> wrote:

>  Hi all,
>
> As I'm trying to write an answer on some French forum about how to do JSF
> in Eclipse, I realize I couldn't find a good link to what JBoss Tools
> provide on this topic.
> I expected to find at least a paragraph about JSF editor from
> http://tools.jboss.org/features/ but couldn't find one. Have I missed it,
> or are we intentionally hiding our JSF tools from that page?
> The same goes for our JavaScript tools and for Visual Preview. I believe
> those are interesting features to highlight and I believe they lack
> visibility from the website.
>
> Should I open a Jira for that?
> --
> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Best Regards,
Ilya Buziuk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/18b830a1/attachment-0001.html 

From mistria at redhat.com  Tue Mar 24 05:22:46 2015
From: mistria at redhat.com (Mickael Istria)
Date: Tue, 24 Mar 2015 10:22:46 +0100
Subject: [jbosstools-dev] Site doesn't mention VPE/VPV,
 JS editor addition nor JSF support?
In-Reply-To: <CADOkA46yWG4GMkYp6vPSqB8NONj2V8=rW=WQ9FFyKxeFnswvjA@mail.gmail.com>
References: <5511272C.8020106@redhat.com>
	<CADOkA46yWG4GMkYp6vPSqB8NONj2V8=rW=WQ9FFyKxeFnswvjA@mail.gmail.com>
Message-ID: <55112CE6.7060505@redhat.com>

On 03/24/2015 10:17 AM, Ilya Buziuk wrote:
> < I expected to find at least a paragraph about JSF editor from 
> http://tools.jboss.org/features/ but couldn't find one
> It's utterly surprising that our users are interested in JSF 
> stuff while when we are deprecating Xulrunner ;-)
It's not yet our users, it's just some people doing JSF and looking for 
good tools. It's more potential users, that we can convert to other 
technologies later.

-- 
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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/41c1ddba/attachment.html 

From manderse at redhat.com  Tue Mar 24 05:33:14 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 24 Mar 2015 05:33:14 -0400 (EDT)
Subject: [jbosstools-dev] Site doesn't mention VPE/VPV,
	JS editor addition nor JSF support?
In-Reply-To: <55112CE6.7060505@redhat.com>
References: <5511272C.8020106@redhat.com>
	<CADOkA46yWG4GMkYp6vPSqB8NONj2V8=rW=WQ9FFyKxeFnswvjA@mail.gmail.com>
	<55112CE6.7060505@redhat.com>
Message-ID: <1968F112-2652-4431-9191-BA580AE13087@redhat.com>

The visual part is not all of jsf. We still have a lot of jsf related features. 

Best way to fix it is to submit pr's to the feature pages :)

/max
http://about.me/maxandersen


> On 24 Mar 2015, at 10:23, Mickael Istria <mistria at redhat.com> wrote:
> 
>> On 03/24/2015 10:17 AM, Ilya Buziuk wrote:
>> < I expected to find at least a paragraph about JSF editor from http://tools.jboss.org/features/ but couldn't find one
>> It's utterly surprising that our users are interested in JSF stuff while when we are deprecating Xulrunner ;-)
> It's not yet our users, it's just some people doing JSF and looking for good tools. It's more potential users, that we can convert to other technologies later.
> 
> -- 
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/3590d18f/attachment.html 

From kmarmaliykov at exadel.com  Tue Mar 24 07:42:00 2015
From: kmarmaliykov at exadel.com (Konstantin Marmalyukov)
Date: Tue, 24 Mar 2015 14:42:00 +0300
Subject: [jbosstools-dev] Site doesn't mention VPE/VPV,
 JS editor addition nor JSF support?
In-Reply-To: <1968F112-2652-4431-9191-BA580AE13087@redhat.com>
References: <5511272C.8020106@redhat.com>	<CADOkA46yWG4GMkYp6vPSqB8NONj2V8=rW=WQ9FFyKxeFnswvjA@mail.gmail.com>	<55112CE6.7060505@redhat.com>
	<1968F112-2652-4431-9191-BA580AE13087@redhat.com>
Message-ID: <55114D88.4080007@exadel.com>

On 3/24/2015 12:33 PM, Max Rydahl Andersen wrote:
> The visual part is not all of jsf. We still have a lot of jsf related 
> features.
>
> Best way to fix it is to submit pr's to the feature pages :)
>
> /max
> http://about.me/maxandersen
>
>
Should we combine info about Visual Editor for JSF files with other JSF 
features or create a Visual Editor feature and write there about both 
HTML and JSF Visual Editors?
> On 24 Mar 2015, at 10:23, Mickael Istria <mistria at redhat.com 
> <mailto:mistria at redhat.com>> wrote:
>
>> On 03/24/2015 10:17 AM, Ilya Buziuk wrote:
>>> < I expected to find at least a paragraph about JSF editor from 
>>> http://tools.jboss.org/features/ but couldn't find one
>>> It's utterly surprising that our users are interested in JSF 
>>> stuff while when we are deprecating Xulrunner ;-)
>> It's not yet our users, it's just some people doing JSF and looking 
>> for good tools. It's more potential users, that we can convert to 
>> other technologies later.
>>
>> -- 
>> 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 at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/5ae8f237/attachment.html 

From ibuziuk at exadel.com  Tue Mar 24 08:28:45 2015
From: ibuziuk at exadel.com (Ilya Buziuk)
Date: Tue, 24 Mar 2015 15:28:45 +0300
Subject: [jbosstools-dev] Site doesn't mention VPE/VPV,
 JS editor addition nor JSF support?
In-Reply-To: <55114D88.4080007@exadel.com>
References: <5511272C.8020106@redhat.com>
	<CADOkA46yWG4GMkYp6vPSqB8NONj2V8=rW=WQ9FFyKxeFnswvjA@mail.gmail.com>
	<55112CE6.7060505@redhat.com>
	<1968F112-2652-4431-9191-BA580AE13087@redhat.com>
	<55114D88.4080007@exadel.com>
Message-ID: <CADOkA44OC+MbQbdKMv7ZJCAEbCz=GV2o0VBQo_+uTYdXtQhfXA@mail.gmail.com>

< Should we combine info about Visual Editor for JSF files with other JSF
features or create a Visual Editor feature and write there about both HTML
and JSF Visual Editors?

Well, frankly I can't see the point of writing about obsolete JSF Visual
Editor, cause, if I understand correctly, it will be completely removed in
JBDS 9. It might be really good to announce deprecation / removal though.
IMHO, it will be relevant to write separately about:
- JSF features (without VPE)
- VPV editor
- HTML preview

P.S. I would also like to add CordovaSim feature to the site.


On Tue, Mar 24, 2015 at 2:42 PM, Konstantin Marmalyukov <
kmarmaliykov at exadel.com> wrote:

>  On 3/24/2015 12:33 PM, Max Rydahl Andersen wrote:
>
> The visual part is not all of jsf. We still have a lot of jsf related
> features.
>
>  Best way to fix it is to submit pr's to the feature pages :)
>
> /max
> http://about.me/maxandersen
>
>
>  Should we combine info about Visual Editor for JSF files with other JSF
> features or create a Visual Editor feature and write there about both HTML
> and JSF Visual Editors?
>
> On 24 Mar 2015, at 10:23, Mickael Istria <mistria at redhat.com> wrote:
>
>   On 03/24/2015 10:17 AM, Ilya Buziuk wrote:
>
> < I expected to find at least a paragraph about JSF editor from
> http://tools.jboss.org/features/ but couldn't find one
> It's utterly surprising that our users are interested in JSF
> stuff while when we are deprecating Xulrunner ;-)
>
> It's not yet our users, it's just some people doing JSF and looking for
> good tools. It's more potential users, that we can convert to other
> technologies later.
>
> --
> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> _______________________________________________
> jbosstools-dev mailing listjbosstools-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>



-- 
Best Regards,
Ilya Buziuk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/d03faac9/attachment.html 

From manderse at redhat.com  Tue Mar 24 11:52:57 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 24 Mar 2015 16:52:57 +0100
Subject: [jbosstools-dev] Proposal to add WTP 3.6.3 feature patch to
 JBT/JBDS target platforms 4.42.0.Final-SNAPSHOT
In-Reply-To: <551072BB.9090704@redhat.com>
References: <55103347.1060505@redhat.com> <551072BB.9090704@redhat.com>
Message-ID: <F5A3D82C-EACF-42A0-AB36-7600AD7FA74E@redhat.com>

I would have expected one or more bundles besides this one feature.group 
  ?

/max

> Here's the p2diff:
>
> ~/tmp/p2diff/p2diff -mode=ignoreVersions -query=groups -onlylatest
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.42.0.Final-SNAPSHOT/REPO/
> file:///home/nboldt/42x/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/
>
>> org.eclipse.wst.jsdt.feature.patch.feature.group 
>> [3.6.3.v201503191608]
> === Summary ===
> file:///home/nboldt/42x/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/
> contains 1 unique IUs
>
> As the TP needs to be published to Nexus *no later than this 
> Wednesday*
> (Code Freeze for 4.2.3.Final is this Thursday), I've pushed this 
> change
> and it's building now [1], so that it will be easier for everyone to
> use/test. If you feel this is a problem, I can of course back out the
> commit.
>
> [1]
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Target-Platforms/job/jbosstoolstargetplatforms-matrix/
>> =382
>
> On 03/23/2015 11:37 AM, Nick Boldt wrote:
>> We need to add a single patch feature and its accompanying single 
>> plugin
>> to the target platform.
>>
>> https://issues.jboss.org/browse/JBDS-3383
>> https://github.com/jbosstools/jbosstools-target-platforms/pull/135
>>
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From mistria at redhat.com  Tue Mar 24 11:54:41 2015
From: mistria at redhat.com (Mickael Istria)
Date: Tue, 24 Mar 2015 16:54:41 +0100
Subject: [jbosstools-dev] Proposal to add WTP 3.6.3 feature patch to
 JBT/JBDS target platforms 4.42.0.Final-SNAPSHOT
In-Reply-To: <F5A3D82C-EACF-42A0-AB36-7600AD7FA74E@redhat.com>
References: <55103347.1060505@redhat.com> <551072BB.9090704@redhat.com>
	<F5A3D82C-EACF-42A0-AB36-7600AD7FA74E@redhat.com>
Message-ID: <551188C1.1030509@redhat.com>

On 03/24/2015 04:52 PM, Max Rydahl Andersen wrote:
> I would have expected one or more bundles besides this one feature.group
>    ?
There is probably, but the "query=groups" parameter hides it.
-- 
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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/dae8966f/attachment.html 

From akazakov at exadel.com  Tue Mar 24 13:12:10 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Tue, 24 Mar 2015 10:12:10 -0700
Subject: [jbosstools-dev] Site doesn't mention VPE/VPV,
 JS editor addition nor JSF support?
In-Reply-To: <1968F112-2652-4431-9191-BA580AE13087@redhat.com>
References: <5511272C.8020106@redhat.com>	<CADOkA46yWG4GMkYp6vPSqB8NONj2V8=rW=WQ9FFyKxeFnswvjA@mail.gmail.com>	<55112CE6.7060505@redhat.com>
	<1968F112-2652-4431-9191-BA580AE13087@redhat.com>
Message-ID: <55119AEA.2040900@exadel.com>

I could create a PR for JSF stuff.

Regarding JS. WDYT if we add a "HTML5/JavaScript" feature. Max asked me 
to create a feature for AngularJS but why don't use some generic name 
and mention all HTML/JS features we want to highlight?
Visual Preview, AngularJS (dynamic content assist), Palette, something else?


On 03/24/2015 02:33 AM, Max Rydahl Andersen wrote:
> The visual part is not all of jsf. We still have a lot of jsf related 
> features.
>
> Best way to fix it is to submit pr's to the feature pages :)
>
> /max
> http://about.me/maxandersen
>
>
> On 24 Mar 2015, at 10:23, Mickael Istria <mistria at redhat.com 
> <mailto:mistria at redhat.com>> wrote:
>
>> On 03/24/2015 10:17 AM, Ilya Buziuk wrote:
>>> < I expected to find at least a paragraph about JSF editor from 
>>> http://tools.jboss.org/features/ but couldn't find one
>>> It's utterly surprising that our users are interested in JSF 
>>> stuff while when we are deprecating Xulrunner ;-)
>> It's not yet our users, it's just some people doing JSF and looking 
>> for good tools. It's more potential users, that we can convert to 
>> other technologies later.
>>
>> -- 
>> 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 at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/a13fcb6c/attachment.html 

From akazakov at exadel.com  Tue Mar 24 13:20:44 2015
From: akazakov at exadel.com (Alexey Kazakov)
Date: Tue, 24 Mar 2015 10:20:44 -0700
Subject: [jbosstools-dev] Site doesn't mention VPE/VPV,
 JS editor addition nor JSF support?
In-Reply-To: <CADOkA44OC+MbQbdKMv7ZJCAEbCz=GV2o0VBQo_+uTYdXtQhfXA@mail.gmail.com>
References: <5511272C.8020106@redhat.com>	<CADOkA46yWG4GMkYp6vPSqB8NONj2V8=rW=WQ9FFyKxeFnswvjA@mail.gmail.com>	<55112CE6.7060505@redhat.com>	<1968F112-2652-4431-9191-BA580AE13087@redhat.com>	<55114D88.4080007@exadel.com>
	<CADOkA44OC+MbQbdKMv7ZJCAEbCz=GV2o0VBQo_+uTYdXtQhfXA@mail.gmail.com>
Message-ID: <55119CEC.5010602@exadel.com>

On 03/24/2015 05:28 AM, Ilya Buziuk wrote:
>
>
> P.S. I would also like to add CordovaSim feature to the site.

Shouldn't we add CordovaSim to the existing Aerogear/Mobile development 
tooling - http://tools.jboss.org/features/aerogear.html ?

>
>
> On Tue, Mar 24, 2015 at 2:42 PM, Konstantin Marmalyukov 
> <kmarmaliykov at exadel.com <mailto:kmarmaliykov at exadel.com>> wrote:
>
>     On 3/24/2015 12:33 PM, Max Rydahl Andersen wrote:
>>     The visual part is not all of jsf. We still have a lot of jsf
>>     related features.
>>
>>     Best way to fix it is to submit pr's to the feature pages :)
>>
>>     /max
>>     http://about.me/maxandersen
>>
>>
>     Should we combine info about Visual Editor for JSF files with
>     other JSF features or create a Visual Editor feature and write
>     there about both HTML and JSF Visual Editors?
>>     On 24 Mar 2015, at 10:23, Mickael Istria <mistria at redhat.com
>>     <mailto:mistria at redhat.com>> wrote:
>>
>>>     On 03/24/2015 10:17 AM, Ilya Buziuk wrote:
>>>>     < I expected to find at least a paragraph about JSF editor from
>>>>     http://tools.jboss.org/features/ but couldn't find one
>>>>     It's utterly surprising that our users are interested in JSF
>>>>     stuff while when we are deprecating Xulrunner ;-)
>>>     It's not yet our users, it's just some people doing JSF and
>>>     looking for good tools. It's more potential users, that we can
>>>     convert to other technologies later.
>>>
>>>     -- 
>>>     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 at lists.jboss.org
>>>     <mailto:jbosstools-dev at lists.jboss.org>
>>>     https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>     _______________________________________________
>>     jbosstools-dev mailing list
>>     jbosstools-dev at lists.jboss.org  <mailto:jbosstools-dev at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>     _______________________________________________
>     jbosstools-dev mailing list
>     jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
>
> -- 
> Best Regards,
> Ilya Buziuk
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/731a9963/attachment.html 

From manderse at redhat.com  Tue Mar 24 14:52:39 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Tue, 24 Mar 2015 14:52:39 -0400 (EDT)
Subject: [jbosstools-dev] Site doesn't mention VPE/VPV,
	JS editor addition nor JSF support?
In-Reply-To: <55119AEA.2040900@exadel.com>
References: <5511272C.8020106@redhat.com>
	<CADOkA46yWG4GMkYp6vPSqB8NONj2V8=rW=WQ9FFyKxeFnswvjA@mail.gmail.com>
	<55112CE6.7060505@redhat.com>
	<1968F112-2652-4431-9191-BA580AE13087@redhat.com>
	<55119AEA.2040900@exadel.com>
Message-ID: <AC5A6EAF-5D90-465B-B3CB-626639F1797A@redhat.com>

+1 for creating a html 5/js  feature section. 

/max
http://about.me/maxandersen


> On 24 Mar 2015, at 18:12, Alexey Kazakov <akazakov at exadel.com> wrote:
> 
> I could create a PR for JSF stuff.
> 
> Regarding JS. WDYT if we add a "HTML5/JavaScript" feature. Max asked me to create a feature for AngularJS but why don't use some generic name and mention all HTML/JS features we want to highlight?
> Visual Preview, AngularJS (dynamic content assist), Palette, something else?
> 
> 
>> On 03/24/2015 02:33 AM, Max Rydahl Andersen wrote:
>> The visual part is not all of jsf. We still have a lot of jsf related features. 
>> 
>> Best way to fix it is to submit pr's to the feature pages :)
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>> On 24 Mar 2015, at 10:23, Mickael Istria <mistria at redhat.com> wrote:
>> 
>>>> On 03/24/2015 10:17 AM, Ilya Buziuk wrote:
>>>> < I expected to find at least a paragraph about JSF editor from http://tools.jboss.org/features/ but couldn't find one
>>>> It's utterly surprising that our users are interested in JSF stuff while when we are deprecating Xulrunner ;-)
>>> It's not yet our users, it's just some people doing JSF and looking for good tools. It's more potential users, that we can convert to other technologies later.
>>> 
>>> -- 
>>> Mickael Istria
>>> Eclipse developer at JBoss, by Red Hat
>>> My blog - My Tweets
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/639e2590/attachment-0001.html 

From nboldt at redhat.com  Tue Mar 24 15:09:53 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Tue, 24 Mar 2015 15:09:53 -0400
Subject: [jbosstools-dev] Proposal to add WTP 3.6.3 feature patch to
 JBT/JBDS target platforms 4.42.0.Final-SNAPSHOT
In-Reply-To: <551188C1.1030509@redhat.com>
References: <55103347.1060505@redhat.com>
	<551072BB.9090704@redhat.com>	<F5A3D82C-EACF-42A0-AB36-7600AD7FA74E@redhat.com>
	<551188C1.1030509@redhat.com>
Message-ID: <5511B681.1080703@redhat.com>

The patch feature includes a single plugin - 
org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar

http://download.jboss.org/jbosstools/updates/requirements/webtools/P-3.6.3-20150319135805/plugins/

So... that's all that's new, beyond the feature.jar.

On 03/24/2015 11:54 AM, Mickael Istria wrote:
> On 03/24/2015 04:52 PM, Max Rydahl Andersen wrote:
>> I would have expected one or more bundles besides this one feature.group
>>    ?
> There is probably, but the "query=groups" parameter hides it.
> --
> 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 at 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

From fbricon at gmail.com  Tue Mar 24 19:57:30 2015
From: fbricon at gmail.com (Fred Bricon)
Date: Tue, 24 Mar 2015 19:57:30 -0400
Subject: [jbosstools-dev] m2e 1.6 M6 is available
Message-ID: <CAG2ouxSrzTWV-Z_zvbX30UAk52A4=1unRYdT6eqKWGgWSctyxA@mail.gmail.com>

Hi,

we've published m2e 1.6 M6 (a.k.a 1.6.0.20150324-2020) to the milestones
repository [1]. The full changelog is available at [2].

This milestone release contains a couple interesting enhancement/bugs fixes
:

- the embedded Maven is now 3.3.1 [3]. Please note Run As > Maven is still
broken though [4]. You'll need to manually
set -Dmaven.multiModuleProjectDirectory in the launch configuration
parameters

- An option to auto update out-of-date project configuration is now
available in the Maven preferences [5]. It's turned off by default since we
*just* found it could cause endless builds in certain circumstances [6].

- The maven archetype plugin has been updated to 2.3 [7]. This fixes a
whole bunch of archetype related issues, which is great. The caveat is some
classes exposed through the very old archetype jars have changed,
"potentially" breaking some 3rd party adopters. Igor mentioned he plans on
moving the archetype features out of m2e-core in the future, as a
consequence, all archetype packages have been flagged as internal [8].

Please give it a try and let us now about any problems you find [9].

Enjoy,

Fred

[1] http://download.eclipse.org/technology/m2e/milestones/1.6/
[2]
https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&list_id=11023199&product=m2e&query_format=advanced&target_milestone=1.6.0%2FMars%20M6
[3] https://bugs.eclipse.org/461881
[4] https://bugs.eclipse.org/462944
[5] https://bugs.eclipse.org/335720
[6] https://bugs.eclipse.org/462898
[7] https://bugs.eclipse.org/336461
[8] https://dev.eclipse.org/mhonarc/lists/m2e-dev/msg01862.html
[9] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=m2e

-- 
"Have you tried turning it off and on again" - The IT Crowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150324/a32b1a46/attachment.html 

From manderse at redhat.com  Wed Mar 25 03:00:34 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Wed, 25 Mar 2015 03:00:34 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201503250700.t2P70YHw009591@int-mx14.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-19500

https://issues.jboss.org/browse/JBIDE-19500
Summary: warn/inform users running on non-compatilbe JVMs they are loosing out on features

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 1 day, 9:13:41.686596

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From mistria at redhat.com  Wed Mar 25 07:34:48 2015
From: mistria at redhat.com (Mickael Istria)
Date: Wed, 25 Mar 2015 12:34:48 +0100
Subject: [jbosstools-dev] Target Platform 4.42.0.Final is released
Message-ID: <55129D58.3060506@redhat.com>

Changes (compared to previous 4.41.2.Final release)
===================================================

* JBDS-3383 : WTP feature patch
* JBIDE-19112: Luna SR2
* JBIDE-19194: minimal-json
* JBIDE-19045 & JBIDE-18869: Move some external deps from TP to pom.xml...

Usage
=====

Target platform 4.42,0,Final is what JBoss Tools 4.2,3.Final will use.
All Jenkins jobs for branch jbosstools-4.2.x and parent pom 4.2.3.Final-SNAPSHOT have been updated to use target platform ${TARGET_PLATFORM_VERSION}.
The following p2 repositories *will be modified* to point to this new target platform while releasing JBoss Tools 4.2.3.Final:
* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/
* http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/

Until then, you can access the target platform at the URLs below.


Download
========

Update site: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.42.0.Final/REPO/
Update site zip: http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstarget/4.42.0.Final/jbosstoolstarget-4.42.0.Final.zip
Git tag: https://github.com/jbosstools/jbosstools-target-platforms/tree/4.42.0.Final


Testing/Development
===================

If your root pom correctly specifies the latest parent pom version as 4.2.3.Final-SNAPSHOT, you need only this
   $ mvn clean verify
If you're using a different parent pom, use this:
   $ mvn clean verify -Dtpc.version=4.42.0.Final

For advanced usage and help (using in IDE, building a mirror locally, using a zip), see:
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.md


What's next?
============

jbosstools-target-platforms project branch 4.42.x has been prepared for potential upgrades, and its version is now 4.42.1.CR1-SNAPSHOT.
We don't expect to keep on working with this branch and don't expect any chamge. But, shall you need anything else, please follow those instructions to request a change ASAP: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc

-- 
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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150325/e395cc2d/attachment.html 

From manderse at redhat.com  Wed Mar 25 10:00:36 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Wed, 25 Mar 2015 15:00:36 +0100
Subject: [jbosstools-dev] Proposal to add WTP 3.6.3 feature patch to
 JBT/JBDS target platforms 4.42.0.Final-SNAPSHOT
In-Reply-To: <5511B681.1080703@redhat.com>
References: <55103347.1060505@redhat.com> <551072BB.9090704@redhat.com>
	<F5A3D82C-EACF-42A0-AB36-7600AD7FA74E@redhat.com>
	<551188C1.1030509@redhat.com> <5511B681.1080703@redhat.com>
Message-ID: <8B4FF663-1BE9-451D-9617-B20D8F5FEBEC@redhat.com>

On 24 Mar 2015, at 20:09, Nick Boldt wrote:

> The patch feature includes a single plugin -
> org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar
>
> http://download.jboss.org/jbosstools/updates/requirements/webtools/P-3.6.3-20150319135805/plugins/
>
> So... that's all that's new, beyond the feature.jar.

okey, good.

but lets remove the query=groups in p2diff in future so the actual diff 
is shown.

/max

>
> On 03/24/2015 11:54 AM, Mickael Istria wrote:
>> On 03/24/2015 04:52 PM, Max Rydahl Andersen wrote:
>>> I would have expected one or more bundles besides this one 
>>> feature.group
>>> ?
>> There is probably, but the "query=groups" parameter hides it.
>> --
>> 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 at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From manderse at redhat.com  Thu Mar 26 03:00:07 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Thu, 26 Mar 2015 03:00:07 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201503260700.t2Q7071J024728@int-mx13.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-19500

https://issues.jboss.org/browse/JBIDE-19500
Summary: warn/inform users running on non-compatilbe JVMs they are loosing out on features

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 2 days, 9:13:14.265974

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From xcoulon at redhat.com  Thu Mar 26 10:45:56 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Thu, 26 Mar 2015 15:45:56 +0100
Subject: [jbosstools-dev] Website update - excluding content from final N&N
Message-ID: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>

Hello,

I just fixed https://issues.jboss.org/browse/JBIDE-19345 <https://issues.jboss.org/browse/JBIDE-19345> which introduces support for conditional directives in the N&N.

From now, you can wrap some content with ifndef::finalnn[] / endif::finalnn[] for N&N items that have been outdated in subsequent versions and thus, that should not appear in the aggregated N&N page of the final release. 
 
See an example here: https://raw.githubusercontent.com/jbosstools/jbosstools-website/master/documentation/whatsnew/forge/forge-news-4.2.3.CR1.adoc : the upgrade to forge 2.15.1.Final is mentioned in the N&N of JBoss Tools 4.2.3.CR1 (which is correct) but it will be hidden in the N&N of JBoss Tools 4.2.3.Final because in the mean time, the Forge runtime has been updated to 2.15.2.Final. 

Best regards,
/Xavier



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150326/be112d72/attachment-0001.html 

From ggastald at redhat.com  Thu Mar 26 10:49:00 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 26 Mar 2015 10:49:00 -0400 (EDT)
Subject: [jbosstools-dev] Website update - excluding content from final
	N&N
In-Reply-To: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
References: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
Message-ID: <20B81760-54F2-44E3-8A3D-D994E4EE9815@redhat.com>

Fantastic! Good job! 
Do we have this documented somewhere?



> Em 26/03/2015, ?s 11:46, Xavier Coulon <xcoulon at redhat.com> escreveu:
> 
> Hello,
> 
> I just fixed https://issues.jboss.org/browse/JBIDE-19345 which introduces support for conditional directives in the N&N.
> 
> From now, you can wrap some content with ifndef::finalnn[] / endif::finalnn[] for N&N items that have been outdated in subsequent versions and thus, that should not appear in the aggregated N&N page of the final release. 
>  
> See an example here: https://raw.githubusercontent.com/jbosstools/jbosstools-website/master/documentation/whatsnew/forge/forge-news-4.2.3.CR1.adoc : the upgrade to forge 2.15.1.Final is mentioned in the N&N of JBoss Tools 4.2.3.CR1 (which is correct) but it will be hidden in the N&N of JBoss Tools 4.2.3.Final because in the mean time, the Forge runtime has been updated to 2.15.2.Final. 
> 
> Best regards,
> /Xavier
> 
> 
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150326/7b600f67/attachment.html 

From xcoulon at redhat.com  Thu Mar 26 10:55:24 2015
From: xcoulon at redhat.com (Xavier Coulon)
Date: Thu, 26 Mar 2015 15:55:24 +0100
Subject: [jbosstools-dev] Website update - excluding content from final
	N&N
In-Reply-To: <20B81760-54F2-44E3-8A3D-D994E4EE9815@redhat.com>
References: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
	<20B81760-54F2-44E3-8A3D-D994E4EE9815@redhat.com>
Message-ID: <9E15386F-5650-4381-8161-5651E5B97C70@redhat.com>

Thanks ! All the credits comes to Asciidoctor guys for making this possible and to Max et al. for finding it.

Sadly no, there isn't much documentation around the website, TBH :-/ but feel free to ask me any question you may have.

Best regards,
/Xavier



> On 26 Mar 2015, at 15:49, George Gastaldi <ggastald at redhat.com> wrote:
> 
> Fantastic! Good job! 
> Do we have this documented somewhere?
> 
> 
> 
> Em 26/03/2015, ?s 11:46, Xavier Coulon <xcoulon at redhat.com <mailto:xcoulon at redhat.com>> escreveu:
> 
>> Hello,
>> 
>> I just fixed https://issues.jboss.org/browse/JBIDE-19345 <https://issues.jboss.org/browse/JBIDE-19345> which introduces support for conditional directives in the N&N.
>> 
>> From now, you can wrap some content with ifndef::finalnn[] / endif::finalnn[] for N&N items that have been outdated in subsequent versions and thus, that should not appear in the aggregated N&N page of the final release. 
>>  
>> See an example here: https://raw.githubusercontent.com/jbosstools/jbosstools-website/master/documentation/whatsnew/forge/forge-news-4.2.3.CR1.adoc <https://raw.githubusercontent.com/jbosstools/jbosstools-website/master/documentation/whatsnew/forge/forge-news-4.2.3.CR1.adoc> : the upgrade to forge 2.15.1.Final is mentioned in the N&N of JBoss Tools 4.2.3.CR1 (which is correct) but it will be hidden in the N&N of JBoss Tools 4.2.3.Final because in the mean time, the Forge runtime has been updated to 2.15.2.Final. 
>> 
>> Best regards,
>> /Xavier
>> 
>> 
>> 
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev <https://lists.jboss.org/mailman/listinfo/jbosstools-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150326/119f0ae8/attachment.html 

From ggastald at redhat.com  Thu Mar 26 13:29:21 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 26 Mar 2015 14:29:21 -0300
Subject: [jbosstools-dev] Website update - excluding content from final
 N&N
In-Reply-To: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
References: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
Message-ID: <551441F1.10704@redhat.com>

One suggestion: Couldn't this be done automatically by the title? Eg: == 
Forge 2 Runtime

On 03/26/2015 11:45 AM, Xavier Coulon wrote:
> Hello,
>
> I just fixed https://issues.jboss.org/browse/JBIDE-19345 which 
> introduces support for conditional directives in the N&N.
>
> From now, you can wrap some content with ifndef::finalnn[] / 
> endif::finalnn[] for N&N items that have been outdated in subsequent 
> versions and thus, that should not appear in the aggregated N&N page 
> of the final release.
> See an example here: 
> https://raw.githubusercontent.com/jbosstools/jbosstools-website/master/documentation/whatsnew/forge/forge-news-4.2.3.CR1.adoc 
> : the upgrade to forge 2.15.1.Final is mentioned in the N&N of JBoss 
> Tools 4.2.3.CR1 (which is correct) but it will be hidden in the N&N of 
> JBoss Tools 4.2.3.Final because in the mean time, the Forge runtime 
> has been updated to 2.15.2.Final.
>
> Best regards,
> /Xavier
>
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20150326/2f3523e6/attachment.html 

From manderse at redhat.com  Thu Mar 26 15:56:21 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 26 Mar 2015 20:56:21 +0100
Subject: [jbosstools-dev] Website update - excluding content from final
 N&N
In-Reply-To: <551441F1.10704@redhat.com>
References: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
	<551441F1.10704@redhat.com>
Message-ID: <D620B021-A359-496F-B35B-3B7BB2BE24AE@redhat.com>

On 26 Mar 2015, at 18:29, George Gastaldi wrote:

> One suggestion: Couldn't this be done automatically by the title? Eg: 
> == Forge 2 Runtime

no. :)

/max

> On 03/26/2015 11:45 AM, Xavier Coulon wrote:
>> Hello,
>>
>> I just fixed https://issues.jboss.org/browse/JBIDE-19345 which 
>> introduces support for conditional directives in the N&N.
>>
>> From now, you can wrap some content with ifndef::finalnn[] / 
>> endif::finalnn[] for N&N items that have been outdated in subsequent 
>> versions and thus, that should not appear in the aggregated N&N page 
>> of the final release.
>> See an example here: 
>> https://raw.githubusercontent.com/jbosstools/jbosstools-website/master/documentation/whatsnew/forge/forge-news-4.2.3.CR1.adoc 
>> : the upgrade to forge 2.15.1.Final is mentioned in the N&N of JBoss 
>> Tools 4.2.3.CR1 (which is correct) but it will be hidden in the N&N 
>> of JBoss Tools 4.2.3.Final because in the mean time, the Forge 
>> runtime has been updated to 2.15.2.Final.
>>
>> Best regards,
>> /Xavier
>>
>>
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From ggastald at redhat.com  Thu Mar 26 16:03:14 2015
From: ggastald at redhat.com (George Gastaldi)
Date: Thu, 26 Mar 2015 17:03:14 -0300
Subject: [jbosstools-dev] Website update - excluding content from final
 N&N
In-Reply-To: <D620B021-A359-496F-B35B-3B7BB2BE24AE@redhat.com>
References: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
	<551441F1.10704@redhat.com>
	<D620B021-A359-496F-B35B-3B7BB2BE24AE@redhat.com>
Message-ID: <55146602.9050305@redhat.com>

Thanks, just checking! :)

On 03/26/2015 04:56 PM, Max Rydahl Andersen wrote:
> On 26 Mar 2015, at 18:29, George Gastaldi wrote:
>
>> One suggestion: Couldn't this be done automatically by the title? Eg: 
>> == Forge 2 Runtime
>
> no. :)
>
> /max
>
>> On 03/26/2015 11:45 AM, Xavier Coulon wrote:
>>> Hello,
>>>
>>> I just fixed https://issues.jboss.org/browse/JBIDE-19345 which 
>>> introduces support for conditional directives in the N&N.
>>>
>>> From now, you can wrap some content with ifndef::finalnn[] / 
>>> endif::finalnn[] for N&N items that have been outdated in subsequent 
>>> versions and thus, that should not appear in the aggregated N&N page 
>>> of the final release.
>>> See an example here: 
>>> https://raw.githubusercontent.com/jbosstools/jbosstools-website/master/documentation/whatsnew/forge/forge-news-4.2.3.CR1.adoc 
>>> : the upgrade to forge 2.15.1.Final is mentioned in the N&N of JBoss 
>>> Tools 4.2.3.CR1 (which is correct) but it will be hidden in the N&N 
>>> of JBoss Tools 4.2.3.Final because in the mean time, the Forge 
>>> runtime has been updated to 2.15.2.Final.
>>>
>>> Best regards,
>>> /Xavier
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen


From manderse at redhat.com  Thu Mar 26 17:23:51 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 26 Mar 2015 22:23:51 +0100
Subject: [jbosstools-dev] Website update - excluding content from final
 N&N
In-Reply-To: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
References: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
Message-ID: <1481BBBC-7C18-4B05-8B01-B725DB8EE853@redhat.com>

On 26 Mar 2015, at 15:45, Xavier Coulon wrote:

> Hello,
>
> I just fixed https://issues.jboss.org/browse/JBIDE-19345 
> <https://issues.jboss.org/browse/JBIDE-19345> which introduces support 
> for conditional directives in the N&N.

Cool. Did you also fix the B part of that Jira ? (to allow adding a 
.Final that gets included in the merge ?)

/max
/max
http://about.me/maxandersen

From manderse at redhat.com  Thu Mar 26 17:33:26 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Thu, 26 Mar 2015 22:33:26 +0100
Subject: [jbosstools-dev] Website update - excluding content from final
 N&N
In-Reply-To: <20B81760-54F2-44E3-8A3D-D994E4EE9815@redhat.com>
References: <FDF28EEB-041A-493A-A22F-E16432D76371@redhat.com>
	<20B81760-54F2-44E3-8A3D-D994E4EE9815@redhat.com>
Message-ID: <83E498F3-5576-4D69-8F40-9B5355969933@redhat.com>

On 26 Mar 2015, at 15:49, George Gastaldi wrote:

> Fantastic! Good job!
> Do we have this documented somewhere?

I added it at 
https://github.com/jbosstools/jbosstools-website#how-do-i-exclude-new-and-noteworthy-content-from-final-version-
together with a few other topics.

grokkable ?

/max

>
>
>
>> Em 26/03/2015, ?s 11:46, Xavier Coulon <xcoulon at redhat.com> 
>> escreveu:
>>
>> Hello,
>>
>> I just fixed https://issues.jboss.org/browse/JBIDE-19345 which 
>> introduces support for conditional directives in the N&N.
>>
>> From now, you can wrap some content with ifndef::finalnn[] / 
>> endif::finalnn[] for N&N items that have been outdated in subsequent 
>> versions and thus, that should not appear in the aggregated N&N page 
>> of the final release.
>>
>> See an example here: 
>> https://raw.githubusercontent.com/jbosstools/jbosstools-website/master/documentation/whatsnew/forge/forge-news-4.2.3.CR1.adoc 
>> : the upgrade to forge 2.15.1.Final is mentioned in the N&N of JBoss 
>> Tools 4.2.3.CR1 (which is correct) but it will be hidden in the N&N 
>> of JBoss Tools 4.2.3.Final because in the mean time, the Forge 
>> runtime has been updated to 2.15.2.Final.
>>
>> Best regards,
>> /Xavier
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen


From manderse at redhat.com  Fri Mar 27 02:59:50 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Fri, 27 Mar 2015 02:59:50 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201503270659.t2R6xoAJ019455@int-mx09.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-19500

https://issues.jboss.org/browse/JBIDE-19500
Summary: warn/inform users running on non-compatilbe JVMs they are loosing out on features

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 3 days, 9:12:57.205122

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From nboldt at redhat.com  Fri Mar 27 10:19:16 2015
From: nboldt at redhat.com (Nick Boldt)
Date: Fri, 27 Mar 2015 10:19:16 -0400
Subject: [jbosstools-dev] JBoss Tools Core 4.2.3.Final bits available for
	community & QE testing
Message-ID: <551566E4.6010409@redhat.com>

As always, these are not FINAL bits, but preliminary results for 
community & QE testing. Not for use by customers or end users.

Update site: http://download.jboss.org/jbosstools/updates/staging/luna/

Target platforms:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Final 

* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.42.0.Final 


Until the above target platform site is released, you may need to add it 
to Eclipse to resolve dependencies at install time.
Once released, dependencies will be found automatically from here:
* 
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ 
(latest release)
* 
http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.42.0.Final-SNAPSHOT/ 
(upcoming milestone)
* 
http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.42.0.Final-SNAPSHOT/ 
(upcoming milestone)

New + noteworthy (subject to change):
* 
https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
* http://tools.jboss.org/documentation/whatsnew/

Schedule: 
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel

--

Additional update sites:
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.Final-updatesite-core/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.Final-updatesite-coretests/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.Final-updatesite-hibernatetools/
* 
http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.3.Final-updatesite-webtools/
and build sites:
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Final-build-core/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Final-build-coretests/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Final-build-hibernatetools/
* 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.3.Final-build-webtools/


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

From manderse at redhat.com  Sun Mar 29 02:59:57 2015
From: manderse at redhat.com (manderse at redhat.com)
Date: Sun, 29 Mar 2015 02:59:57 -0400
Subject: [jbosstools-dev] ACTION REQUIRED: 1 issue with no component
Message-ID: <201503290659.t2T6xvPK017915@int-mx09.intmail.prod.int.phx2.redhat.com>


This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!

 
* No component for JBIDE-19533

https://issues.jboss.org/browse/JBIDE-19533
Summary: Missing schemas for WildFly configuration 

Assignee: None set - please fix.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 19:40:50.065342

----------------------------



Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

From manderse at redhat.com  Fri Mar 27 13:15:35 2015
From: manderse at redhat.com (Max Rydahl Andersen)
Date: Fri, 27 Mar 2015 18:15:35 +0100
Subject: [jbosstools-dev] rename "testing-tools" to "arquillian"
In-Reply-To: <98D69EBA-E484-48B3-8C42-7EAB2DF03282@redhat.com>
References: <98D69EBA-E484-48B3-8C42-7EAB2DF03282@redhat.com>
Message-ID: <3C2D814E-587A-47A0-AB0B-0B2CA22B7735@redhat.com>

Since no objections this have now changed.

testing-tools -> arquillian in JBIDE and added to jbds

> Hi,
>
> when we creatd "testing-tools" component is was to cover what at the
> time was a sea of testing
> fwks like arquillian, shrinkwrap, httpunit, jsfunit etc. but over time
> it is now 99% arquillian.
>
> Normally I would have marked testingt-tools as deprecated and name it zz
> testing-tools and add
> new "arquillian" component.
>
> but that seems overkill in this case.
>
> If no objections to this I'll do the rename by Tuesday.
>
> Thanks,
> /max
> http://about.me/maxandersen
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen