subject:"\[Dev\] \[DEV\] \[VOTE\] WSO2 Developer Studio Tooling for Platform RC2"

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-28 Thread Jasintha Dasanayake

Hi All

Actually the original issue is , ESB 5.0.0 server cannot start in Developer
Studio with carbon server 4.4 in DevS 3.8.0 as well as 4.1.0 ( this was
reported by several  people) , I also able to reproduce this issue with
DevS 3.8.0 and ESB 5.0.0 Alpa , I am getting the following error in DevS
 console when server is starting

"Invalid initial heap size: -XmsMEM_OPTS=-Xms256m -Xmx1024m

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.
"
I debug the code and found the root cause for this error ,

  VM parameters has been defined in the carbon.definition.xml [1] as follows


org.wso2.carbon.bootstrap.Bootstrap
${carbon.home}
-Xms256m -Xmx1024m -XX:MaxPermSize=256m
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath="${carbon.home}/repository/logs/heap-dump.hprof"
-Dcom.sun.management.jmxremote
-Djava.endorsed.dirs="${carbon.home}/lib/endorsed"
-Djava.io.tmpdir="${carbon.home}/tmp"
-Dcatalina.base="${carbon.home}/lib/tomcat" -Dwso2.server.standalone=true
-Dcarbon.registry.root=/ -Dcarbon.home="${carbon.home}"
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Dcarbon.config.dir.path="${carbon.home}/repository/conf"
-Djava.util.logging.config.file="${carbon.home}/repository/conf/etc/logging-bridge.properties"
-Dcomponents.repo="${carbon.home}/repository/components/plugins"
-Dconf.location="${carbon.home}/repository/conf"
-Dcom.atomikos.icatch.file="${carbon.home}/lib/transactions.properties"
-Dcom.atomikos.icatch.hide_init_file_path=true
-Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
-Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
-Dcom.sun.jndi.ldap.connect.pool.authentication=simple
-Dcom.sun.jndi.ldap.connect.pool.timeout=3000
-Dorg.terracotta.quartz.skipUpdateCheck=true
-Djava.security.egd=file:/dev/./urandom -Dfile.encoding=UTF8
-Djava.net.preferIPv4Stack=true -Dcom.ibm.cacheLocalHost=true
-DworkerNode=false

carbon.libs
${carbon.debug}



There is a class called "CarbonServerScriptParser"[2] , it has been used to
read the server startup sh line by line and try to figure out  the these  -Xms
-Xmx -XX:MaxPermSize  three values from server sh , it has the  following
logic to find out these values

FileReader fileReader = new FileReader(scriptFile);

BufferedReader reader = new BufferedReader(fileReader);


 String line = reader.readLine();

  while (line != null) {

if (line.contains(MIN_MEMORY_STRING)) {

String[] array = line.split(" ");

for (String string : array) {

if (string.contains(MIN_MEMORY_STRING)) {

vmParams.put(MIN_MEMORY_STRING,string.trim().substring(MIN_MEMORY_STRING
.length()));

}

}

  }

According to above logic it's read line by line and use "string.contains(
MIN_MEMORY_STRING)" method to match and find above VM argument values.
Above Min Memory VM augment  is defined in the ESB 5.0.0 server startup
file in the following way

JVM_MEM_OPTS="-Xms256m -Xmx1024m"

so when pass this line result will be "MEM_OPTS="-Xms256m"  , then original
VM param value  which is define in the carbon.definition.xml file, will be
overwritten using this value , (this is happening in there server imple
class[3] ( method  getVmArguments()) As a result of this above exception is
printed to the console

However IMO what we are trying to do here is not necessary, because eclipse
has a built in UI to configure these VM arguments before the server start,
so we shouldn't need to get it from server startup script , if a user want
to change those default values users can easily configure it using eclipse
it self  furthermore  we have done this for port configuration similar we
can do it for VM arguments configuration

Thanks and Regards
/Jasintha


[1] -
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml

[2]-
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver.base/src/org/wso2/developerstudio/eclipse/carbonserver/base/utils/CarbonServerScriptParser.java

[3]-
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver.base/src/org/wso2/developerstudio/eclipse/carbonserver/base/impl/CarbonServerBehaviour.java



On Sat, May 28, 2016 at 7:26 AM, Awanthika Senarath 
wrote:

> Thanks Susankha,
>
> [+ Kavith]
>
> Will have a look at this,
>
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Sat, May 28, 2016 at 4:31 AM, Susankha Nirmala 
> wrote:
>
>>
>>
>> On Fri, May 27, 2016 at 4:01 PM, Susankha Nirmala 
>> wrote:
>>
>>> I was able to start ESB 5.0.0 using DevStudio 3.8.0 (with carbonserver
>>> 4.4) with Java 1.7 and 1.8. Because, as I explained, in the DevS 3.8 we are
>>> passing "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters(refer [1]).
>>> Attached the

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-27 Thread Awanthika Senarath

Thanks Susankha,

[+ Kavith]

Will have a look at this,



Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Sat, May 28, 2016 at 4:31 AM, Susankha Nirmala  wrote:

>
>
> On Fri, May 27, 2016 at 4:01 PM, Susankha Nirmala 
> wrote:
>
>> I was able to start ESB 5.0.0 using DevStudio 3.8.0 (with carbonserver
>> 4.4) with Java 1.7 and 1.8. Because, as I explained, in the DevS 3.8 we are
>> passing "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters(refer [1]).
>> Attached the screenshots to the mail.
>>
>>  @ Awanthika,
>>
>> You can pass the same "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
>> parameters in the DevStudio 4.1.0 (revert relevant changes in the commit
>> [2]). When you are testing, don't test with the selfhost devstudio, and
>> build the p2 locally and install that to fresh eclipse Mars pack.
>>
>> [1]-
>> https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>> [2]-
>> https://github.com/wso2/devstudio-tooling-platform/commit/e17477078563fc145da99a5460a6ef18af385822#diff-54e1d0cafafda5466af0c4671299155b
>>
>> Thanks.
>> /Susankha.
>>
>
>
>
>
>>
>> On Thu, May 26, 2016 at 9:45 PM, Susankha Nirmala 
>> wrote:
>>
>>>
>>> On Thu, May 26, 2016 at 9:02 PM, Awanthika Senarath 
>>> wrote:
>>>
 Hello Susankha,

 We cannot have those VM arguments in serverdefinition.xml as ESB 5.0.0
 which is based on carbon 4.4.1 has a different wso2carbon.sh which will not
 be able to start if we pass those VM arguments. So the option is to
 integrate a new server for carbon 4.4.1.

>>>
>>> ESB 5.0.0 is using the Carbon Kernel version 4.4.5 and in the
>>> "wso2server.sh" carbon file, it will check the Java version like below and
>>> assign the values of the VM parameters to the "JVM_MEM_OPTS" variable,
>>> according to the java version. Then use the "$JVM_MEM_OPTS" parameter in
>>> the
>>> system property section (refer [1])
>>>
>>>
>>> if [ -z "$JVM_MEM_OPTS" ]; then
>>>java_version=$("$JAVACMD" -version 2>&1 | awk -F '"' '/version/
>>> {print $2}')
>>>JVM_MEM_OPTS="-Xms256m -Xmx1024m"
>>>if [ "$java_version" \< "1.8" ]; then
>>>   JVM_MEM_OPTS="$JVM_MEM_OPTS -XX:MaxPermSize=256m"
>>>fi
>>> fi
>>>
>>> .
>>>
>>> while [ "$status" = "$START_EXIT_STATUS" ]
>>> do
>>> $JAVACMD \
>>> -Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
>>> $JVM_MEM_OPTS \
>>>
>>> Without creating a new server for ESB 5.0.0 (Carbon Kernel 4.4.5), we
>>> can use the same CarbonServer44 component.
>>> We can check the JAVA version and according to that, we can set the
>>> relavent VM parameters.
>>> I think that is the best way to handle this issue, without introduce a
>>> new CarbonSever vertion inside the DevStudio.
>>>
>>>
>>> [1]-
>>> https://github.com/wso2/carbon-kernel/blob/v4.4.5/distribution/kernel/carbon-home/bin/wso2server.sh
>>>
>>>
>>>
>>>



 Regards
 Awanthika

 Awanthika Senarath
 Software Engineer, WSO2 Inc.
 Mobile: +94717681791



 On Fri, May 27, 2016 at 9:15 AM, Susankha Nirmala 
 wrote:

>
>
> On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala 
> wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake <
>> jasin...@wso2.com> wrote:
>>
>>>
>>>
>>> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath <
>>> awanth...@wso2.com> wrote:
>>>
 Hello Nuwan,

 Please find my comments inline,

 I have noticed following issues while testing.


 https://wso2.org/jira/browse/TOOLS-3412

 As I have mentioned before this is a OS specific issue which comes
 in Linux and not a blocker. We will attempt to fix this as we move on.

 https://wso2.org/jira/browse/TOOLS-3416

>>>
>>> Actually this issue happens only when the server is started in JDK
>>> 1.7 if server runs on JDK 1.8 this issue won't be there , reason for 
>>> this
>>> issue is ,  memory settings are defined in two different ways for JDK 7 
>>> and
>>> 8  in carbons server , So we have to find  a way to distinguish  these 
>>> two
>>> settings inside the eclipse
>>>
>>
>>
>> This error happens due to missing "-Xms256m -Xmx1024m -XX:
>> MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 
>> 5.0.0
>> is support for Java 1.7.0 and 1.8.0 (refer [3]).
>> ESB 4.9.0 also supported for both Java versions and in the
>> carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
>> -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].
>>
>> With the Java 1.8, PermSize VM parameter not using, because in Java 8

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-27 Thread Susankha Nirmala

I was able to start ESB 5.0.0 using DevStudio 3.8.0 (with carbonserver 4.4)
with Java 1.7 and 1.8. Because, as I explained, in the DevS 3.8 we are
passing "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters(refer [1]).
Attached the screenshots to the mail.

 @ Awanthika,

You can pass the same "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
parameters in the DevStudio 4.1.0 (revert relevant changes in the commit
[2]). When you are testing, don't test with the selfhost devstudio, and
build the p2 locally and install that to fresh eclipse Mars pack.

[1]-
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
[2]-
https://github.com/wso2/devstudio-tooling-platform/commit/e17477078563fc145da99a5460a6ef18af385822#diff-54e1d0cafafda5466af0c4671299155b

Thanks.
/Susankha.

On Thu, May 26, 2016 at 9:45 PM, Susankha Nirmala  wrote:

>
> On Thu, May 26, 2016 at 9:02 PM, Awanthika Senarath 
> wrote:
>
>> Hello Susankha,
>>
>> We cannot have those VM arguments in serverdefinition.xml as ESB 5.0.0
>> which is based on carbon 4.4.1 has a different wso2carbon.sh which will not
>> be able to start if we pass those VM arguments. So the option is to
>> integrate a new server for carbon 4.4.1.
>>
>
> ESB 5.0.0 is using the Carbon Kernel version 4.4.5 and in the
> "wso2server.sh" carbon file, it will check the Java version like below and
> assign the values of the VM parameters to the "JVM_MEM_OPTS" variable,
> according to the java version. Then use the "$JVM_MEM_OPTS" parameter in
> the
> system property section (refer [1])
>
>
> if [ -z "$JVM_MEM_OPTS" ]; then
>java_version=$("$JAVACMD" -version 2>&1 | awk -F '"' '/version/ {print
> $2}')
>JVM_MEM_OPTS="-Xms256m -Xmx1024m"
>if [ "$java_version" \< "1.8" ]; then
>   JVM_MEM_OPTS="$JVM_MEM_OPTS -XX:MaxPermSize=256m"
>fi
> fi
>
> .
>
> while [ "$status" = "$START_EXIT_STATUS" ]
> do
> $JAVACMD \
> -Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
> $JVM_MEM_OPTS \
>
> Without creating a new server for ESB 5.0.0 (Carbon Kernel 4.4.5), we can
> use the same CarbonServer44 component.
> We can check the JAVA version and according to that, we can set the
> relavent VM parameters.
> I think that is the best way to handle this issue, without introduce a new
> CarbonSever vertion inside the DevStudio.
>
>
> [1]-
> https://github.com/wso2/carbon-kernel/blob/v4.4.5/distribution/kernel/carbon-home/bin/wso2server.sh
>
>
>
>
>>
>>
>>
>> Regards
>> Awanthika
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Fri, May 27, 2016 at 9:15 AM, Susankha Nirmala 
>> wrote:
>>
>>>
>>>
>>> On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala 
>>> wrote:
>>>


 On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake  wrote:

>
>
> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath <
> awanth...@wso2.com> wrote:
>
>> Hello Nuwan,
>>
>> Please find my comments inline,
>>
>> I have noticed following issues while testing.
>>
>>
>> https://wso2.org/jira/browse/TOOLS-3412
>>
>> As I have mentioned before this is a OS specific issue which comes in
>> Linux and not a blocker. We will attempt to fix this as we move on.
>>
>> https://wso2.org/jira/browse/TOOLS-3416
>>
>
> Actually this issue happens only when the server is started in JDK 1.7
> if server runs on JDK 1.8 this issue won't be there , reason for this 
> issue
> is ,  memory settings are defined in two different ways for JDK 7 and 8  
> in
> carbons server , So we have to find  a way to distinguish  these two
> settings inside the eclipse
>


 This error happens due to missing "-Xms256m -Xmx1024m -XX:
 MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
 is support for Java 1.7.0 and 1.8.0 (refer [3]).
 ESB 4.9.0 also supported for both Java versions and in the
 carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
 -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].

 With the Java 1.8, PermSize VM parameter not using, because in Java 8
 PermGen is replace with Metaspace. But we need to support Both Java
 versions (1.7 and 1.8).
 We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
 parameters and when we are starting server in Java 1.8.0 it will give the
 following warning, but continue the starting process.

 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
 MaxPermSize=256m; support was removed in 8.0

 If you directly run ESB with Java 1.8.0, you can see above warning log.
 The best thing we can do is use the same VM parameters define in the
 wso2carbon.sh file

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-26 Thread Susankha Nirmala

On Thu, May 26, 2016 at 9:02 PM, Awanthika Senarath 
wrote:

> Hello Susankha,
>
> We cannot have those VM arguments in serverdefinition.xml as ESB 5.0.0
> which is based on carbon 4.4.1 has a different wso2carbon.sh which will not
> be able to start if we pass those VM arguments. So the option is to
> integrate a new server for carbon 4.4.1.
>

ESB 5.0.0 is using the Carbon Kernel version 4.4.5 and in the
"wso2server.sh" carbon file, it will check the Java version like below and
assign the values of the VM parameters to the "JVM_MEM_OPTS" variable,
according to the java version. Then use the "$JVM_MEM_OPTS" parameter in
the
system property section (refer [1])


if [ -z "$JVM_MEM_OPTS" ]; then
   java_version=$("$JAVACMD" -version 2>&1 | awk -F '"' '/version/ {print
$2}')
   JVM_MEM_OPTS="-Xms256m -Xmx1024m"
   if [ "$java_version" \< "1.8" ]; then
  JVM_MEM_OPTS="$JVM_MEM_OPTS -XX:MaxPermSize=256m"
   fi
fi

.

while [ "$status" = "$START_EXIT_STATUS" ]
do
$JAVACMD \
-Xbootclasspath/a:"$CARBON_XBOOTCLASSPATH" \
$JVM_MEM_OPTS \

Without creating a new server for ESB 5.0.0 (Carbon Kernel 4.4.5), we can
use the same CarbonServer44 component.
We can check the JAVA version and according to that, we can set the
relavent VM parameters.
I think that is the best way to handle this issue, without introduce a new
CarbonSever vertion inside the DevStudio.


[1]-
https://github.com/wso2/carbon-kernel/blob/v4.4.5/distribution/kernel/carbon-home/bin/wso2server.sh




>
>
>
> Regards
> Awanthika
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Fri, May 27, 2016 at 9:15 AM, Susankha Nirmala 
> wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala 
>> wrote:
>>
>>>
>>>
>>> On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake 
>>> wrote:
>>>


 On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath  wrote:

> Hello Nuwan,
>
> Please find my comments inline,
>
> I have noticed following issues while testing.
>
>
> https://wso2.org/jira/browse/TOOLS-3412
>
> As I have mentioned before this is a OS specific issue which comes in
> Linux and not a blocker. We will attempt to fix this as we move on.
>
> https://wso2.org/jira/browse/TOOLS-3416
>

 Actually this issue happens only when the server is started in JDK 1.7
 if server runs on JDK 1.8 this issue won't be there , reason for this issue
 is ,  memory settings are defined in two different ways for JDK 7 and 8  in
 carbons server , So we have to find  a way to distinguish  these two
 settings inside the eclipse

>>>
>>>
>>> This error happens due to missing "-Xms256m -Xmx1024m -XX:
>>> MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
>>> is support for Java 1.7.0 and 1.8.0 (refer [3]).
>>> ESB 4.9.0 also supported for both Java versions and in the
>>> carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
>>> -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].
>>>
>>> With the Java 1.8, PermSize VM parameter not using, because in Java 8
>>> PermGen is replace with Metaspace. But we need to support Both Java
>>> versions (1.7 and 1.8).
>>> We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
>>> parameters and when we are starting server in Java 1.8.0 it will give the
>>> following warning, but continue the starting process.
>>>
>>> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>>> MaxPermSize=256m; support was removed in 8.0
>>>
>>> If you directly run ESB with Java 1.8.0, you can see above warning log.
>>> The best thing we can do is use the same VM parameters define in the
>>> wso2carbon.sh file in the carbon.definition.xml (that's what we have done
>>> with carbonserver 4.2 and that's why we can't see
>>> This issue, when starting ESB 4.9.0 with Java 1.7.0)
>>>
>>> [1]-
>>> https://github.com/wso2/devstudio-tooling-platform/blob/developer-studio-tooling-platform-4.1.0-beta2/plugins/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>>> [2]-
>>> https://github.com/wso2/devstudio-tooling-platform/blob/master/plugins/org.wso2.developerstudio.eclipse.carbonserver42/serverdefinition/carbon.definition.xml
>>> [3]- https://docs.wso2.com/display/ESB500/Installation+Prerequisites
>>>
>>> Thanks.
>>> /Susankha.
>>>
>>
>>
>> With the DevStudio 3.8.0 also we can run carbon44 servers and but there
>> we can see "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters ([1])
>>
>> [1]-
>> https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>>
>>
>>
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>

 Thanks and Regards
 /Jasintha

>
> We will look into this. It appears that

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-26 Thread Awanthika Senarath

Hello Susankha,

We cannot have those VM arguments in serverdefinition.xml as ESB 5.0.0
which is based on carbon 4.4.1 has a different wso2carbon.sh which will not
be able to start if we pass those VM arguments. So the option is to
integrate a new server for carbon 4.4.1.



Regards
Awanthika

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Fri, May 27, 2016 at 9:15 AM, Susankha Nirmala  wrote:

>
>
> On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala 
> wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake 
>> wrote:
>>
>>>
>>>
>>> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath 
>>> wrote:
>>>
 Hello Nuwan,

 Please find my comments inline,

 I have noticed following issues while testing.


 https://wso2.org/jira/browse/TOOLS-3412

 As I have mentioned before this is a OS specific issue which comes in
 Linux and not a blocker. We will attempt to fix this as we move on.

 https://wso2.org/jira/browse/TOOLS-3416

>>>
>>> Actually this issue happens only when the server is started in JDK 1.7
>>> if server runs on JDK 1.8 this issue won't be there , reason for this issue
>>> is ,  memory settings are defined in two different ways for JDK 7 and 8  in
>>> carbons server , So we have to find  a way to distinguish  these two
>>> settings inside the eclipse
>>>
>>
>>
>> This error happens due to missing "-Xms256m -Xmx1024m -XX:
>> MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
>> is support for Java 1.7.0 and 1.8.0 (refer [3]).
>> ESB 4.9.0 also supported for both Java versions and in the
>> carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
>> -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].
>>
>> With the Java 1.8, PermSize VM parameter not using, because in Java 8
>> PermGen is replace with Metaspace. But we need to support Both Java
>> versions (1.7 and 1.8).
>> We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
>> parameters and when we are starting server in Java 1.8.0 it will give the
>> following warning, but continue the starting process.
>>
>> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
>> MaxPermSize=256m; support was removed in 8.0
>>
>> If you directly run ESB with Java 1.8.0, you can see above warning log.
>> The best thing we can do is use the same VM parameters define in the
>> wso2carbon.sh file in the carbon.definition.xml (that's what we have done
>> with carbonserver 4.2 and that's why we can't see
>> This issue, when starting ESB 4.9.0 with Java 1.7.0)
>>
>> [1]-
>> https://github.com/wso2/devstudio-tooling-platform/blob/developer-studio-tooling-platform-4.1.0-beta2/plugins/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>> [2]-
>> https://github.com/wso2/devstudio-tooling-platform/blob/master/plugins/org.wso2.developerstudio.eclipse.carbonserver42/serverdefinition/carbon.definition.xml
>> [3]- https://docs.wso2.com/display/ESB500/Installation+Prerequisites
>>
>> Thanks.
>> /Susankha.
>>
>
>
> With the DevStudio 3.8.0 also we can run carbon44 servers and but there we
> can see "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters ([1])
>
> [1]-
> https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
>
>
>
>
>>
>>
>>
>>
>>
>>
>>
>>>
>>> Thanks and Regards
>>> /Jasintha
>>>

 We will look into this. It appears that this is caused by a memory leak
 due to non heap-size setting[1] by the configurations.


 [1] https://github.com/spring-projects/spring-boot/issues/4376




 Regards
 Awanthika



 Awanthika Senarath
 Software Engineer, WSO2 Inc.
 Mobile: +94717681791



 On Thu, May 26, 2016 at 8:50 AM, Sohani Weerasinghe 
 wrote:

> Hi All,
>
> I have tested the updater tool functionality including installing
> features and no major issues found
>
> @Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.
>
> [1] https://wso2.org/jira/browse/TOOLS-3416
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela 
> wrote:
>
>> Hi All,
>>
>> I have noticed following issues while testing.
>> https://wso2.org/jira/browse/TOOLS-3412
>> https://wso2.org/jira/browse/TOOLS-3416
>>
>> Thanks,
>> Nuwan
>>
>> On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa <
>> heshit...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I have tested

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-26 Thread Susankha Nirmala

On Thu, May 26, 2016 at 8:26 PM, Susankha Nirmala  wrote:

>
>
> On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake 
> wrote:
>
>>
>>
>> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath 
>> wrote:
>>
>>> Hello Nuwan,
>>>
>>> Please find my comments inline,
>>>
>>> I have noticed following issues while testing.
>>>
>>>
>>> https://wso2.org/jira/browse/TOOLS-3412
>>>
>>> As I have mentioned before this is a OS specific issue which comes in
>>> Linux and not a blocker. We will attempt to fix this as we move on.
>>>
>>> https://wso2.org/jira/browse/TOOLS-3416
>>>
>>
>> Actually this issue happens only when the server is started in JDK 1.7 if
>> server runs on JDK 1.8 this issue won't be there , reason for this issue is
>> ,  memory settings are defined in two different ways for JDK 7 and 8  in
>> carbons server , So we have to find  a way to distinguish  these two
>> settings inside the eclipse
>>
>
>
> This error happens due to missing "-Xms256m -Xmx1024m -XX:
> MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
> is support for Java 1.7.0 and 1.8.0 (refer [3]).
> ESB 4.9.0 also supported for both Java versions and in the
> carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
> -Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].
>
> With the Java 1.8, PermSize VM parameter not using, because in Java 8
> PermGen is replace with Metaspace. But we need to support Both Java
> versions (1.7 and 1.8).
> We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
> parameters and when we are starting server in Java 1.8.0 it will give the
> following warning, but continue the starting process.
>
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
> MaxPermSize=256m; support was removed in 8.0
>
> If you directly run ESB with Java 1.8.0, you can see above warning log.
> The best thing we can do is use the same VM parameters define in the
> wso2carbon.sh file in the carbon.definition.xml (that's what we have done
> with carbonserver 4.2 and that's why we can't see
> This issue, when starting ESB 4.9.0 with Java 1.7.0)
>
> [1]-
> https://github.com/wso2/devstudio-tooling-platform/blob/developer-studio-tooling-platform-4.1.0-beta2/plugins/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
> [2]-
> https://github.com/wso2/devstudio-tooling-platform/blob/master/plugins/org.wso2.developerstudio.eclipse.carbonserver42/serverdefinition/carbon.definition.xml
> [3]- https://docs.wso2.com/display/ESB500/Installation+Prerequisites
>
> Thanks.
> /Susankha.
>


With the DevStudio 3.8.0 also we can run carbon44 servers and but there we
can see "-Xms256m -Xmx1024m -XX:MaxPermSize=256m" VM parameters ([1])

[1]-
https://github.com/wso2/developer-studio/blob/developer-studio-3.8.0/server/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml




>
>
>
>
>
>
>
>>
>> Thanks and Regards
>> /Jasintha
>>
>>>
>>> We will look into this. It appears that this is caused by a memory leak
>>> due to non heap-size setting[1] by the configurations.
>>>
>>>
>>> [1] https://github.com/spring-projects/spring-boot/issues/4376
>>>
>>>
>>>
>>>
>>> Regards
>>> Awanthika
>>>
>>>
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> On Thu, May 26, 2016 at 8:50 AM, Sohani Weerasinghe 
>>> wrote:
>>>
 Hi All,

 I have tested the updater tool functionality including installing
 features and no major issues found

 @Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.

 [1] https://wso2.org/jira/browse/TOOLS-3416

 Sohani Weerasinghe
 Software Engineer
 WSO2, Inc: http://wso2.com

 Mobile  : +94 716439774
 Blog :http://christinetechtips.blogspot.com/
 Twitter  : https://twitter.com/sohanichristine

 On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela 
 wrote:

> Hi All,
>
> I have noticed following issues while testing.
> https://wso2.org/jira/browse/TOOLS-3412
> https://wso2.org/jira/browse/TOOLS-3416
>
> Thanks,
> Nuwan
>
> On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa <
> heshit...@wso2.com> wrote:
>
>> Hi all,
>>
>> I have tested BPS Tooling with the new platform and no major issues
>> found.
>>
>> +1
>>
>> Thanks.
>>
>> On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya > > wrote:
>>
>>> Hi all,
>>>
>>> I have tested the project nature extension point and found no issues.
>>>
>>> +1
>>>
>>> Thanks,
>>> Maheeka
>>>
>>> Maheeka Jayasuriya
>>> Software Engineer
>>> Mobile : +9450661
>>>
>>> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath <
>>> awanth...@wso2.com> wrote:
>>>
 Hello Devs,

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-26 Thread Susankha Nirmala

On Thu, May 26, 2016 at 7:18 PM, Jasintha Dasanayake 
wrote:

>
>
> On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath 
> wrote:
>
>> Hello Nuwan,
>>
>> Please find my comments inline,
>>
>> I have noticed following issues while testing.
>>
>>
>> https://wso2.org/jira/browse/TOOLS-3412
>>
>> As I have mentioned before this is a OS specific issue which comes in
>> Linux and not a blocker. We will attempt to fix this as we move on.
>>
>> https://wso2.org/jira/browse/TOOLS-3416
>>
>
> Actually this issue happens only when the server is started in JDK 1.7 if
> server runs on JDK 1.8 this issue won't be there , reason for this issue is
> ,  memory settings are defined in two different ways for JDK 7 and 8  in
> carbons server , So we have to find  a way to distinguish  these two
> settings inside the eclipse
>


This error happens due to missing "-Xms256m -Xmx1024m -XX:
MaxPermSize=256m" VM parameters in the carbon.definition.xml[1]. ESB 5.0.0
is support for Java 1.7.0 and 1.8.0 (refer [3]).
ESB 4.9.0 also supported for both Java versions and in the
carbon.definition.xml file of the carbonserver 4.2, we can see "-Xms256m
-Xmx1024m -XX:MaxPermSize=256m" VM parameters[2].

With the Java 1.8, PermSize VM parameter not using, because in Java 8
PermGen is replace with Metaspace. But we need to support Both Java
versions (1.7 and 1.8).
We can pass same three "-Xms256m -Xmx1024m -XX: MaxPermSize=256m" VM
parameters and when we are starting server in Java 1.8.0 it will give the
following warning, but continue the starting process.

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=256m; support was removed in 8.0

If you directly run ESB with Java 1.8.0, you can see above warning log.
The best thing we can do is use the same VM parameters define in the
wso2carbon.sh file in the carbon.definition.xml (that's what we have done
with carbonserver 4.2 and that's why we can't see
This issue, when starting ESB 4.9.0 with Java 1.7.0)

[1]-
https://github.com/wso2/devstudio-tooling-platform/blob/developer-studio-tooling-platform-4.1.0-beta2/plugins/org.wso2.developerstudio.eclipse.carbonserver44/serverdefinition/carbon.definition.xml
[2]-
https://github.com/wso2/devstudio-tooling-platform/blob/master/plugins/org.wso2.developerstudio.eclipse.carbonserver42/serverdefinition/carbon.definition.xml
[3]- https://docs.wso2.com/display/ESB500/Installation+Prerequisites

Thanks.
/Susankha.







>
> Thanks and Regards
> /Jasintha
>
>>
>> We will look into this. It appears that this is caused by a memory leak
>> due to non heap-size setting[1] by the configurations.
>>
>>
>> [1] https://github.com/spring-projects/spring-boot/issues/4376
>>
>>
>>
>>
>> Regards
>> Awanthika
>>
>>
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Thu, May 26, 2016 at 8:50 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I have tested the updater tool functionality including installing
>>> features and no major issues found
>>>
>>> @Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.
>>>
>>> [1] https://wso2.org/jira/browse/TOOLS-3416
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela 
>>> wrote:
>>>
 Hi All,

 I have noticed following issues while testing.
 https://wso2.org/jira/browse/TOOLS-3412
 https://wso2.org/jira/browse/TOOLS-3416

 Thanks,
 Nuwan

 On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa  wrote:

> Hi all,
>
> I have tested BPS Tooling with the new platform and no major issues
> found.
>
> +1
>
> Thanks.
>
> On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya 
> wrote:
>
>> Hi all,
>>
>> I have tested the project nature extension point and found no issues.
>>
>> +1
>>
>> Thanks,
>> Maheeka
>>
>> Maheeka Jayasuriya
>> Software Engineer
>> Mobile : +9450661
>>
>> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath <
>> awanth...@wso2.com> wrote:
>>
>>> Hello Devs,
>>>
>>>
>>> We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio 
>>> Tooling
>>> for Platform 4.1.0.*
>>>
>>> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0
>>> is available here
>>> .
>>>  Source
>>> and Tag Location to be voted upon is available here
>>> 
>>> .
>>>

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-26 Thread Jasintha Dasanayake

On Thu, May 26, 2016 at 9:05 AM, Awanthika Senarath 
wrote:

> Hello Nuwan,
>
> Please find my comments inline,
>
> I have noticed following issues while testing.
>
>
> https://wso2.org/jira/browse/TOOLS-3412
>
> As I have mentioned before this is a OS specific issue which comes in
> Linux and not a blocker. We will attempt to fix this as we move on.
>
> https://wso2.org/jira/browse/TOOLS-3416
>

Actually this issue happens only when the server is started in JDK 1.7 if
server runs on JDK 1.8 this issue won't be there , reason for this issue is
,  memory settings are defined in two different ways for JDK 7 and 8  in
carbons server , So we have to find  a way to distinguish  these two
settings inside the eclipse

Thanks and Regards
/Jasintha

>
> We will look into this. It appears that this is caused by a memory leak
> due to non heap-size setting[1] by the configurations.
>
>
> [1] https://github.com/spring-projects/spring-boot/issues/4376
>
>
>
>
> Regards
> Awanthika
>
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Thu, May 26, 2016 at 8:50 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> I have tested the updater tool functionality including installing
>> features and no major issues found
>>
>> @Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.
>>
>> [1] https://wso2.org/jira/browse/TOOLS-3416
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela  wrote:
>>
>>> Hi All,
>>>
>>> I have noticed following issues while testing.
>>> https://wso2.org/jira/browse/TOOLS-3412
>>> https://wso2.org/jira/browse/TOOLS-3416
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa 
>>> wrote:
>>>
 Hi all,

 I have tested BPS Tooling with the new platform and no major issues
 found.

 +1

 Thanks.

 On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya 
 wrote:

> Hi all,
>
> I have tested the project nature extension point and found no issues.
>
> +1
>
> Thanks,
> Maheeka
>
> Maheeka Jayasuriya
> Software Engineer
> Mobile : +9450661
>
> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath <
> awanth...@wso2.com> wrote:
>
>> Hello Devs,
>>
>>
>> We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio 
>> Tooling
>> for Platform 4.1.0.*
>>
>> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
>> available here
>> .
>>  Source
>> and Tag Location to be voted upon is available here
>> 
>> .
>>
>> Developer Studio 4.1.0  Tooling for Platform is released on Developer
>> Studio kernel 4.1.0
>> Developer Studio Kernel contains a single feature which has the
>> bundles that are required to implement WSO2 specific product tooling on
>> Eclipse.
>>
>>- This release contains Developer Studio migration to Eclipse mars
>>- Improvements in the Developer Studio Updater tool for automatic
>>updates
>>
>>
>>
>>1. [+] Stable - go ahead and release
>>2. [-]  Broken - do not release (please explain why)
>>
>>
>> The platform could to be tested on top of Developer Studio Kernel
>> with compatible tooling SNAPSHOT versions available at [1].
>>
>>
>> [1]
>> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/
>>
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Heshitha Hettihewa
 *Software Engineer*
 Mobile : +94716866386
 <%2B94%20%280%29%20773%20451194>
 heshit...@wso2.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-25 Thread Awanthika Senarath

Hello Nuwan,

Please find my comments inline,

I have noticed following issues while testing.


https://wso2.org/jira/browse/TOOLS-3412

As I have mentioned before this is a OS specific issue which comes in Linux
and not a blocker. We will attempt to fix this as we move on.

https://wso2.org/jira/browse/TOOLS-3416


We will look into this. It appears that this is caused by a memory leak due
to non heap-size setting[1] by the configurations.


[1] https://github.com/spring-projects/spring-boot/issues/4376




Regards
Awanthika



Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Thu, May 26, 2016 at 8:50 AM, Sohani Weerasinghe  wrote:

> Hi All,
>
> I have tested the updater tool functionality including installing features
> and no major issues found
>
> @Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.
>
> [1] https://wso2.org/jira/browse/TOOLS-3416
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela  wrote:
>
>> Hi All,
>>
>> I have noticed following issues while testing.
>> https://wso2.org/jira/browse/TOOLS-3412
>> https://wso2.org/jira/browse/TOOLS-3416
>>
>> Thanks,
>> Nuwan
>>
>> On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested BPS Tooling with the new platform and no major issues
>>> found.
>>>
>>> +1
>>>
>>> Thanks.
>>>
>>> On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya 
>>> wrote:
>>>
 Hi all,

 I have tested the project nature extension point and found no issues.

 +1

 Thanks,
 Maheeka

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath  wrote:

> Hello Devs,
>
>
> We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio 
> Tooling
> for Platform 4.1.0.*
>
> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
> available here
> .
>  Source
> and Tag Location to be voted upon is available here
> 
> .
>
> Developer Studio 4.1.0  Tooling for Platform is released on Developer
> Studio kernel 4.1.0
> Developer Studio Kernel contains a single feature which has the
> bundles that are required to implement WSO2 specific product tooling on
> Eclipse.
>
>- This release contains Developer Studio migration to Eclipse mars
>- Improvements in the Developer Studio Updater tool for automatic
>updates
>
>
>
>1. [+] Stable - go ahead and release
>2. [-]  Broken - do not release (please explain why)
>
>
> The platform could to be tested on top of Developer Studio Kernel with
> compatible tooling SNAPSHOT versions available at [1].
>
>
> [1]
> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Heshitha Hettihewa
>>> *Software Engineer*
>>> Mobile : +94716866386
>>> <%2B94%20%280%29%20773%20451194>
>>> heshit...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>@*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-25 Thread Sohani Weerasinghe

Hi All,

I have tested the updater tool functionality including installing features
and no major issues found

@Nuwan: I have tested [1] in Linux and couldn't reproduce the issue.

[1] https://wso2.org/jira/browse/TOOLS-3416

Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine

On Wed, May 25, 2016 at 6:02 PM, Nuwan Pallewela  wrote:

> Hi All,
>
> I have noticed following issues while testing.
> https://wso2.org/jira/browse/TOOLS-3412
> https://wso2.org/jira/browse/TOOLS-3416
>
> Thanks,
> Nuwan
>
> On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa 
> wrote:
>
>> Hi all,
>>
>> I have tested BPS Tooling with the new platform and no major issues found.
>>
>> +1
>>
>> Thanks.
>>
>> On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested the project nature extension point and found no issues.
>>>
>>> +1
>>>
>>> Thanks,
>>> Maheeka
>>>
>>> Maheeka Jayasuriya
>>> Software Engineer
>>> Mobile : +9450661
>>>
>>> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath 
>>> wrote:
>>>
 Hello Devs,


 We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio 
 Tooling
 for Platform 4.1.0.*

 P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
 available here
 .
  Source
 and Tag Location to be voted upon is available here
 
 .

 Developer Studio 4.1.0  Tooling for Platform is released on Developer
 Studio kernel 4.1.0
 Developer Studio Kernel contains a single feature which has the bundles
 that are required to implement WSO2 specific product tooling on Eclipse.

- This release contains Developer Studio migration to Eclipse mars
- Improvements in the Developer Studio Updater tool for automatic
updates



1. [+] Stable - go ahead and release
2. [-]  Broken - do not release (please explain why)


 The platform could to be tested on top of Developer Studio Kernel with
 compatible tooling SNAPSHOT versions available at [1].


 [1]
 http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/


 Awanthika Senarath
 Software Engineer, WSO2 Inc.
 Mobile: +94717681791



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Heshitha Hettihewa
>> *Software Engineer*
>> Mobile : +94716866386
>> <%2B94%20%280%29%20773%20451194>
>> heshit...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-25 Thread Nuwan Pallewela

Hi All,

I have noticed following issues while testing.
https://wso2.org/jira/browse/TOOLS-3412
https://wso2.org/jira/browse/TOOLS-3416

Thanks,
Nuwan

On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa 
wrote:

> Hi all,
>
> I have tested BPS Tooling with the new platform and no major issues found.
>
> +1
>
> Thanks.
>
> On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya 
> wrote:
>
>> Hi all,
>>
>> I have tested the project nature extension point and found no issues.
>>
>> +1
>>
>> Thanks,
>> Maheeka
>>
>> Maheeka Jayasuriya
>> Software Engineer
>> Mobile : +9450661
>>
>> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath 
>> wrote:
>>
>>> Hello Devs,
>>>
>>>
>>> We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio 
>>> Tooling
>>> for Platform 4.1.0.*
>>>
>>> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
>>> available here
>>> .
>>>  Source
>>> and Tag Location to be voted upon is available here
>>> 
>>> .
>>>
>>> Developer Studio 4.1.0  Tooling for Platform is released on Developer
>>> Studio kernel 4.1.0
>>> Developer Studio Kernel contains a single feature which has the bundles
>>> that are required to implement WSO2 specific product tooling on Eclipse.
>>>
>>>- This release contains Developer Studio migration to Eclipse mars
>>>- Improvements in the Developer Studio Updater tool for automatic
>>>updates
>>>
>>>
>>>
>>>1. [+] Stable - go ahead and release
>>>2. [-]  Broken - do not release (please explain why)
>>>
>>>
>>> The platform could to be tested on top of Developer Studio Kernel with
>>> compatible tooling SNAPSHOT versions available at [1].
>>>
>>>
>>> [1]
>>> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/
>>>
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-25 Thread Heshitha Hettihewa

Hi all,

I have tested BPS Tooling with the new platform and no major issues found.

+1

Thanks.

On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya 
wrote:

> Hi all,
>
> I have tested the project nature extension point and found no issues.
>
> +1
>
> Thanks,
> Maheeka
>
> Maheeka Jayasuriya
> Software Engineer
> Mobile : +9450661
>
> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath 
> wrote:
>
>> Hello Devs,
>>
>>
>> We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio 
>> Tooling
>> for Platform 4.1.0.*
>>
>> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
>> available here
>> .
>>  Source
>> and Tag Location to be voted upon is available here
>> 
>> .
>>
>> Developer Studio 4.1.0  Tooling for Platform is released on Developer
>> Studio kernel 4.1.0
>> Developer Studio Kernel contains a single feature which has the bundles
>> that are required to implement WSO2 specific product tooling on Eclipse.
>>
>>- This release contains Developer Studio migration to Eclipse mars
>>- Improvements in the Developer Studio Updater tool for automatic
>>updates
>>
>>
>>
>>1. [+] Stable - go ahead and release
>>2. [-]  Broken - do not release (please explain why)
>>
>>
>> The platform could to be tested on top of Developer Studio Kernel with
>> compatible tooling SNAPSHOT versions available at [1].
>>
>>
>> [1]
>> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/
>>
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Heshitha Hettihewa
*Software Engineer*
Mobile : +94716866386
<%2B94%20%280%29%20773%20451194>
heshit...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-25 Thread Maheeka Jayasuriya

Hi all,

I have tested the project nature extension point and found no issues.

+1

Thanks,
Maheeka

Maheeka Jayasuriya
Software Engineer
Mobile : +9450661

On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath 
wrote:

> Hello Devs,
>
>
> We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio Tooling
> for Platform 4.1.0.*
>
> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
> available here
> .
>  Source
> and Tag Location to be voted upon is available here
> 
> .
>
> Developer Studio 4.1.0  Tooling for Platform is released on Developer
> Studio kernel 4.1.0
> Developer Studio Kernel contains a single feature which has the bundles
> that are required to implement WSO2 specific product tooling on Eclipse.
>
>- This release contains Developer Studio migration to Eclipse mars
>- Improvements in the Developer Studio Updater tool for automatic
>updates
>
>
>
>1. [+] Stable - go ahead and release
>2. [-]  Broken - do not release (please explain why)
>
>
> The platform could to be tested on top of Developer Studio Kernel with
> compatible tooling SNAPSHOT versions available at [1].
>
>
> [1]
> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/
>
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-23 Thread Awanthika Senarath

Hello Devs,


We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio Tooling
for Platform 4.1.0.*

P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
available here
.
Source
and Tag Location to be voted upon is available here

.

Developer Studio 4.1.0  Tooling for Platform is released on Developer
Studio kernel 4.1.0
Developer Studio Kernel contains a single feature which has the bundles
that are required to implement WSO2 specific product tooling on Eclipse.

   - This release contains Developer Studio migration to Eclipse mars
   - Improvements in the Developer Studio Updater tool for automatic updates



   1. [+] Stable - go ahead and release
   2. [-]  Broken - do not release (please explain why)


The platform could to be tested on top of Developer Studio Kernel with
compatible tooling SNAPSHOT versions available at [1].


[1]
http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/


Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

[Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

14 matches

Site Navigation

Mail list logo

Footer information