Date   
GlassFish-5.0-b08 is promoted and available for download

Arindam Bandyopadhyay
 

The latest GlassFish 5.0 promotion i.e glassfish-5.0-b08 is available for download. It can be downloaded from the following location

Following important changes are included in this build

Component updates

  • JSON-P 1.1
  • javax.servlet-api 4.0.0-b06
  • JAX-RS 2.1-m07
  • Jersey 2.26-b04
  • JavaMail 1.6.0-rc2
  • Grizzly 2.4.0-beta8

Bugs Fixed

GitHub Issue ID
Description
21627
"Description" is not displayed in "JMS Connection Factories"
21741
The number of times EJB create method is called is incorrect in Jconsole
21138
After editing Availability service in configurations domain.xml corrupted
21764
Regression in secure admin
21687
CDI devtests are failing after Mojarra to 2.3.0-m10 integration

    Weekly promotions go through more thorough testing but if you want
    to use the latest, you can pick up the nightly bits from here.
    Do try out the bits and share your experience with us.
    
-- 
Thanks,
Arindam

Re: Archived Projects - I have a high interest in the Wiseman project

Guillermo González de Agüero
 

Hi David,

I imagine this also applies to my request to recover the Java EE tutorial sources, no?


Regards,

Guillermo González de Agüero

El mié., 7 de junio de 2017 12:41, David Delabassee <david.delabassee@...> escribió:
Michael,
 
We will evaluate your request once the migration of 'core' projects will be entirely done.

It is anyway interresting to see that project such as Wiseman still have some traction.
 
--David

Re: GlassFish-5.0-b08 is promoted and available for download

Gunnar Morling
 

Hi,

It seems this build does not yet integrate Bean Validation 2.0 (JSR 380) and its reference implementation Hibernate Validator 6. Is there any timeline for doing this update? If there is anything I can help with, please let me know.

--Gunnar

Re: GlassFish-5.0-b08 is promoted and available for download

yamini.k.b@...
 

Hi Gunnar,

Yes, we are planning to integrate BV 2.0 soon but I can’t commit on a date yet. Thanks for offering to help, we will reach out to you if required.

-Yamini

On Jun 7, 2017, at 6:59 PM, Gunnar Morling via Groups.Io <gunnar.morling@...> wrote:

Hi,

It seems this build does not yet integrate Bean Validation 2.0 (JSR 380) and its reference implementation Hibernate Validator 6. Is there any timeline for doing this update? If there is anything I can help with, please let me know.

--Gunnar

Re: Java EE tutorial sources

David Delabassee
 

Hi,

That archived project seems to be an unmaintainted and partial snapshot of an older version of the Java EE Tutorial (Java EE 5 or 6). In addition, it is in a proprietary format (Frame Maker?); I can only read some metadata so I'm not even sure?!. So clearly there's no point to export that specific project at this stage.

Now it would be great to see the community stepping in to help create tutorials. Don't you think that it would just be more pragmatic to create specific, to the point, tutorials on specific aspects of Java EE 8?

--David

Re: Java EE tutorial sources

 

This is definitely something the community could help do. There have certainly been people in the past that have talked about this. Should we coordinate folks right now or should we wait a bit? Do you have concrete ideas on how to proceed?

-------- Original message --------
From: David Delabassee <david.delabassee@...>
Date: 6/7/17 11:13 AM (GMT-05:00)
To: glassfish@javaee.groups.io
Subject: Re: [gf] Java EE tutorial sources

Hi,

That archived project seems to be an unmaintainted and partial snapshot of an older version of the Java EE Tutorial (Java EE 5 or 6). In addition, it is in a proprietary format (Frame Maker?); I can only read some metadata so I'm not even sure?!. So clearly there's no point to export that specific project at this stage.

Now it would be great to see the community stepping in to help create tutorials. Don't you think that it would just be more pragmatic to create specific, to the point, tutorials on specific aspects of Java EE 8?

--David

Re: Java EE tutorial sources

Guillermo González de Agüero
 

Hi David,

Thanks for your response. I really thought that open source tutorial was the EE 7 one.

Any chance to open source the current ones? Java EE being an open and participative standard would benefit from having also an open documentation so the community can contribute on some missing (or little documented) features, like JASPIC. 

There was also a Jira project for the tutorial. Was it also for the old version? Where should we give feedback now?

I agree with your point about the EE 8 community tutorials you mention, and I know there are already some initiatives emerging, but I'd still like to see an "official" and central place to contribute.


Regards,

Guillermo González de Agüero


El mié., 7 de junio de 2017 17:13, David Delabassee <david.delabassee@...> escribió:
Hi,

That archived project seems to be an unmaintainted and partial snapshot of an older version of the Java EE Tutorial (Java EE 5 or 6). In addition, it is in a proprietary format (Frame Maker?); I can only read some metadata so I'm not even sure?!. So clearly there's no point to export that specific project at this stage.

Now it would be great to see the community stepping in to help create tutorials. Don't you think that it would just be more pragmatic to create specific, to the point, tutorials on specific aspects of Java EE 8?

--David

Re: Java EE tutorial sources

moltenma@...
 

Hi,
I agree with the idea to ask the community to create the the tutorials, you can easily collect many (too many?) tutorials.
I think a coordinator (collect the tutorials, define priorities, interaction with the authors etc) and at least a couple of reviewers (definition of the quality/acceptance criteria) are required.
Why not to ask to some 'eminent' Java champions or JSR leaders to give set a good example and prepare some signed quality tutorials to start?

Marco

On Wed, Jun 7, 2017 at 5:57 PM, reza_rahman <reza_rahman@...> wrote:
This is definitely something the community could help do. There have certainly been people in the past that have talked about this. Should we coordinate folks right now or should we wait a bit? Do you have concrete ideas on how to proceed?

-------- Original message --------
From: David Delabassee <david.delabassee@...>
Date: 6/7/17 11:13 AM (GMT-05:00)
Subject: Re: [gf] Java EE tutorial sources

Hi,

That archived project seems to be an unmaintainted and partial snapshot of an older version of the Java EE Tutorial (Java EE 5 or 6). In addition, it is in a proprietary format (Frame Maker?); I can only read some metadata so I'm not even sure?!. So clearly there's no point to export that specific project at this stage.

Now it would be great to see the community stepping in to help create tutorials. Don't you think that it would just be more pragmatic to create specific, to the point, tutorials on specific aspects of Java EE 8?

--David


Re: Java EE tutorial sources

David Delabassee
 

You're right, we had an issue tracker for the Tutorial.
Let me discuss that and your other suggestions internally first.

--David

Structural change in GlassFish code

Arindam Bandyopadhyay
 

We are planing to make the following changes in GlassFish source code structure to cleanup the repository.

1.Delete 'V2' directory - In time of GitHub migration, we have refactored the old trunk/v2/appserv-tests and put all valid tests under main/appserver/tests/appserv-tests/devtests in the GlassFish repository. Under top level v2/appserv-tests, we kept only those tests that haven't been refactored(mostly they are legacy and not running in CI). Instead of putting v2/ as a top level directory,we would be moving it under appserver/tests/v2-tests.

2.Delete copyright module - 'copyright' module is there in top level GlassFish repository just to hold a single file copyright-exclude.Moreover removing it would simplify running the copyright checks on the GlassFish workspace (remove the pre-requisite of building the copyright module)
We would split the configuration and maintain copyright excludes in different parts of the workspace.
E.g:
nucleus/pom.xml
appserver/pom.xml
appserver/tests/pom.xml

3.Remove top level 'main' directory:In time of GitHub migration, we split glassfish~svn and created logical repositories. 'main' directory was there to separate GlassFish code from other code that used to reside under glassfish~svn/trunk. Post GitHub migration, as we have separate repository for each of the sub projects, now GlassFish GitHub repository contains only GlassFish source code. As main becomes redundant now, I am planing to remove 'main'.

Post refactoring, the top level directories/files would be
.github
appserver
nucleus
.gitignore
CONTRIBUTING.md
LICENSE
README.md
pom.xml

I have logged issue 21822 for this change.We are planing to push this changes in GlassFish GitHub repository early next week. If you have scripts that depend on the current directory structure, please update it after the change is pushed.
-- 
Thanks,
Arindam

Strang RQ failure on Pull Request 21831

Edward Burns
 

Hello GlassFish team,

I issued PR 21831 and tried to run the CI tests, they ran with this job <http://gf-hudson.us.oracle.com/hudson/job/gf-remote-queue/460/>. This job has a strange error:

==== VERSION INFO ====

+++ git rev-parse --short HEAD
++ CURRENT_COMMIT=9955c9e2af
++ echo Git Revision: 9955c9e2af
+++ git branch
+++ cut -d ' ' -f 2
+++ grep '^*'
++ echo Git Branch: pull-request-21831
+++ date
++ echo Build Date: Mon Jun 12 12:58:59 PDT 2017
++ '[' '' = weekly ']'
++ '[' '!' -z ']'
++ export CURRENT_COMMIT
++ dev_build
++ printf '\n%s \n\n' '===== DO THE BUILD! ====='

===== DO THE BUILD! =====

++ mvn -Dmaven.repo.local=/scratch/BUILD_AREA/workspace/gf-remote-queue/repository -C -nsu -B -f pom.xml clean install -Dmaven.test.failure.ignore=true
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-readable POM /scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml: /scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml (No such file or directory) @
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project (/scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml) has 1 error
[ERROR] Non-readable POM /scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml: /scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml (No such file or directory)
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
Test is Running=true
Status for PR=21831 is BUILD_FAILED
Sending test run end email for PR=21831with email id=null
[FINDBUGS] Skipping publisher since build result is FAILURE
Recording test results
Archiving artifacts
Checking UNSTABLE | FAILURE | ABORTED
Hudson Text Finder: File set 'test-results/test-status.txt' is empty
Finished: FAILURE


How can I move this forward?

Thanks,

Ed

Re: Strang RQ failure on Pull Request 21831

Arindam Bandyopadhyay
 

Hi Ed,

This is due to my changes in the build system for the bug #21822.We are restructuring GlassFish code and removing the main directory. I am going to merge the fix (PR #21828) by tomorrow. After that I would restart the pipeline for your PR#21831 .

Thanks,
Arindam

On Tuesday 13 June 2017 01:45 AM, Edward Burns wrote:
Hello GlassFish team,

I issued PR 21831 and tried to run the CI tests, they ran with this job <http://gf-hudson.us.oracle.com/hudson/job/gf-remote-queue/460/>. This job has a strange error:

==== VERSION INFO ====

+++ git rev-parse --short HEAD
++ CURRENT_COMMIT=9955c9e2af
++ echo Git Revision: 9955c9e2af
+++ git branch
+++ cut -d ' ' -f 2
+++ grep '^*'
++ echo Git Branch: pull-request-21831
+++ date
++ echo Build Date: Mon Jun 12 12:58:59 PDT 2017
++ '[' '' = weekly ']'
++ '[' '!' -z ']'
++ export CURRENT_COMMIT
++ dev_build
++ printf '\n%s \n\n' '===== DO THE BUILD! ====='

===== DO THE BUILD! =====

++ mvn -Dmaven.repo.local=/scratch/BUILD_AREA/workspace/gf-remote-queue/repository -C -nsu -B -f pom.xml clean install -Dmaven.test.failure.ignore=true
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-readable POM /scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml: /scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml (No such file or directory) @
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project (/scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml) has 1 error
[ERROR] Non-readable POM /scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml: /scratch/BUILD_AREA/workspace/gf-remote-queue/glassfish/pom.xml (No such file or directory)
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
Test is Running=true
Status for PR=21831 is BUILD_FAILED
Sending test run end email for PR=21831with email id=null
[FINDBUGS] Skipping publisher since build result is FAILURE
Recording test results
Archiving artifacts
Checking UNSTABLE | FAILURE | ABORTED
Hudson Text Finder: File set 'test-results/test-status.txt' is empty
Finished: FAILURE


How can I move this forward?

Thanks,

Ed

Re: Strang RQ failure on Pull Request 21831

Edward Burns
 

On Tue, 13 Jun 2017 02:05:32 +0530, "Arindam Bandyopadhyay" <arindam.bandyopadhyay@...> said:
AB> Hi Ed,
AB> This is due to my changes in the build system for the bug #21822.We are
AB> restructuring GlassFish code and removing the main directory. I am going
AB> to merge the fix (PR #21828) by tomorrow. After that I would restart the
AB> pipeline for your PR#21831 .

Yes, I had seen that mail but wasn't sure that was the cause.

Thanks.

Ed

--
| @edburns | office: +1 407 458 0017

Request for Java EE 7 tutorial Codes.

amwangi4@...
 

Hi, 
 
I hope this email finds you well. I was requesting for the codes examples for Java EE 7 tutorial. Thanks.
 
Kind Regards,
Aaron Mwangi.

Re: Request for Java EE 7 tutorial Codes.

David Delabassee
 

Hi Aaron,

The sources of the different examples can be found in the Java EE SDK bundle; see http://www.oracle.com/technetwork/java/javaee/downloads/java-ee-sdk-7-downloads-1956236.html

--David

Re: Structural change in GlassFish code

Arindam Bandyopadhyay
 

We have merged the change with javaee/glassfish master. Please refer Pull Request [1] for details.
Please make sure you update your branch in your Fork origin.

git checkout <your local branch>
git fetch upstream master  [Assuming upstream is javaee/glassfish ]
git merge upstream/master
git push origin <your remote branch>

[1]https://github.com/javaee/glassfish/pull/21828

Thanks,
Arindam

Reg: Archived JavaEE projects

Vigneswaran Sitaraman
 

I need access to some of the archived JavaEE projects source code.   Projects like openinstaller, petstore, etc.

Re: Reg: Archived JavaEE projects

David Delabassee
 

We will look at that after we are done with the migration.
We will only consider to make available the projects which might still partly be relevant and I doubt OpenInstaller will fall in that category.

--David

Re: Request for Java EE 7 tutorial Codes.

Ondrej Mihályi
 

Hi David,

What about the tutorial itself? Can the community somehow help with updating the tutorial to EE 8? Some areas aren't even updated to EE 7 and I know there are many people eager to help update the tutorial.
Would it make sense to create a repository where others could send contributions, which would then be used as a material for the tutorial? Can we edit the tutorial content to improve it and offer it back to Oracle?

--Ondro

Re: Request for Java EE 7 tutorial Codes.

David Delabassee
 

Regarding open sourcing the tutorial itself, there are some technical issues that we first need to solve like the fact that it is currently in a proprietary format. We would need to first convert it to something that it's usable and contributor friendly (e.g. Asciidoc or MD). In addition, the fact that tutorial in itself is huge (nearly 1000 pages!) doesn't really simplify the conversion discussions.

It's not commitment but we are looking at this as we would like to allow the community to enhance the tutorial.

--David