Stephane Talbot (JIRA | 28 Jul 00:40 2015
Picon

[jira] [Updated] (GERONIMODEVTOOLS-813) Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars


     [
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Talbot updated GERONIMODEVTOOLS-813:
---------------------------------------------
    Description: 
Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars.
If you try to install Geronimo v3.0 Server Adapter	3.0.1, the installation fails with the following error:
{quote}
Cannot complete the install because one or more required items could not be found.
  Software being installed: Geronimo v3.0 Server Adapter 3.0.1
(org.apache.geronimo.v30.feature.feature.group 3.0.1)
  Missing requirement: Geronimo Server Tools V30 UI Plug-in 3.0.1 (org.apache.geronimo.st.v30.ui
3.0.1) requires 'bundle org.eclipse.tm.terminal.view [2.1.0,4.0.0)' but it could not be found
  Cannot satisfy dependency:
    From: Geronimo v3.0 Server Adapter 3.0.1 (org.apache.geronimo.v30.feature.feature.group 3.0.1)
    To: org.apache.geronimo.st.v30.ui [3.0.1]
{quote}

In fact Mars p2 repositories doesn't provide 
- org.eclipse.tm.terminal 
- org.eclipse.tm.terminal.view 
- org.eclipse.tm.terminal.ssh
- org.eclipse.tm.terminal.telnet
required by org.apache.geronimo.st.v30.ui 3.0.1.

In fact these osgi bundles are not anymore in TM 4.0 which is sent with eclipse 4.5.

You have to add  the Luna's repositories in P2 (either http://download.eclipse.org/releases/luna/ or
(Continue reading)

Stephane Talbot (JIRA | 28 Jul 00:35 2015
Picon

[jira] [Updated] (GERONIMODEVTOOLS-813) Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars


     [
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Talbot updated GERONIMODEVTOOLS-813:
---------------------------------------------
    Description: 
Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars.
If you try to install Geronimo v3.0 Server Adapter	3.0.1, the installation fails with the following error:
{quote}
Cannot complete the install because one or more required items could not be found.
  Software being installed: Geronimo v3.0 Server Adapter 3.0.1
(org.apache.geronimo.v30.feature.feature.group 3.0.1)
  Missing requirement: Geronimo Server Tools V30 UI Plug-in 3.0.1 (org.apache.geronimo.st.v30.ui
3.0.1) requires 'bundle org.eclipse.tm.terminal.view [2.1.0,4.0.0)' but it could not be found
  Cannot satisfy dependency:
    From: Geronimo v3.0 Server Adapter 3.0.1 (org.apache.geronimo.v30.feature.feature.group 3.0.1)
    To: org.apache.geronimo.st.v30.ui [3.0.1]
{quote}

In fact Mars p2 repositories doesn't provide 
- org.eclipse.tm.terminal 
- org.eclipse.tm.terminal.view 
- org.eclipse.tm.terminal.ssh
- org.eclipse.tm.terminal.telnet
required by org.apache.geronimo.st.v30.ui 3.0.1.

In fact these osgi bundles are not anymore in TM 4.0 which is sent with eclipse 4.5

> Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars
(Continue reading)

Stephane Talbot (JIRA | 28 Jul 00:09 2015
Picon

[jira] [Updated] (GERONIMODEVTOOLS-813) Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars


     [
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Talbot updated GERONIMODEVTOOLS-813:
---------------------------------------------
    Component/s: eclipse-plugin

> Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars
> -----------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-813
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-813
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 3.0.1
>            Reporter: Stephane Talbot
>            Priority: Minor
>

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Stephane Talbot (JIRA | 28 Jul 00:09 2015
Picon

[jira] [Updated] (GERONIMODEVTOOLS-813) Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars


     [
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Talbot updated GERONIMODEVTOOLS-813:
---------------------------------------------
    Affects Version/s: 3.0.1

> Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars
> -----------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-813
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-813
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 3.0.1
>            Reporter: Stephane Talbot
>            Priority: Minor
>

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Stephane Talbot (JIRA | 28 Jul 00:09 2015
Picon

[jira] [Updated] (GERONIMODEVTOOLS-813) Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars


     [
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Talbot updated GERONIMODEVTOOLS-813:
---------------------------------------------
    Summary: Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars  (was: Geronimo Eclipse Plugin 3.0.1 Released)

> Geronimo Eclipse Plugin 3.0.1 don't install in eclipse mars
> -----------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-813
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-813
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 3.0.1
>            Reporter: Stephane Talbot
>            Priority: Minor
>

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Stephane Talbot (JIRA | 28 Jul 00:08 2015
Picon

[jira] [Created] (GERONIMODEVTOOLS-813) Geronimo Eclipse Plugin 3.0.1 Released

Stephane Talbot created GERONIMODEVTOOLS-813:
------------------------------------------------

             Summary: Geronimo Eclipse Plugin 3.0.1 Released
                 Key: GERONIMODEVTOOLS-813
                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-813
             Project: Geronimo-Devtools
          Issue Type: Bug
            Reporter: Stephane Talbot
            Priority: Minor

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Alan D. Cabrera | 9 Jul 07:11 2015

Board report time 2015-07

Here's the report that I sent to the board:
https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2015-07+-+July
If I missed something please let me know directly.  I’m sorry about being so tardy with the report.


Regards,
Alan

Romain Manni-Bucau | 6 Jul 16:54 2015
Picon

xbean 4.4

Hi guys,

identified https://issues.apache.org/jira/browse/XBEAN-286 and therefore I'd like to release ti let depending projects upgrading ASAP.

Anyone having something pending? Happy to wait few days to have a "bigger" release.

PS: think we already discussed it but can't recall and find the answer: why don't we use 3 digits for xbean? like doing a 4.3.1 now.

Romain Manni-Bucau
<at> rmannibucau |  Blog | Github | LinkedIn | Tomitriber
Rory O'Donnell | 2 Jul 10:43 2015
Picon

Geronimo dependencies on JDK-Internal APIs


Hi ,

My name is Rory O'Donnell, I am the OpenJDK Quality Group Lead. 

I'm contacting you because your open source project seems to be a very popular dependency for other open source projects.
As part of the preparations for JDK 9, Oracle’s engineers have been analyzing open source projects like yours to understand usage. One area of concern involves identifying compatibility problems, such as reliance on JDK-internal APIs.

Our engineers have already prepared guidance on migrating some of the more common usage patterns of JDK-internal APIs to supported public interfaces.  The list is on the OpenJDK wiki [0].

As part of the ongoing development of JDK 9, I would like to inquire about your usage of  JDK-internal APIs and to encourage migration towards supported Java APIs if necessary.

The first step is to identify if your application(s) is leveraging internal APIs.

  Step 1: Download JDeps.
Just download a preview release of JDK8(JDeps Download). You do not need to actually test or run your application on JDK8.  JDeps(Docs) looks through JAR files and identifies which JAR files use internal APIs and then lists those APIs.   
  Step 2: To run JDeps against an application. The command looks like:
jdk8/bin/jdeps -P -jdkinternals *.jar > your-application.jdeps.txt

The output inside your-application.jdeps.txt will look like:

your.package (Filename.jar)
      -> com.sun.corba.se            JDK internal API (rt.jar)
3rd party library using Internal APIs:
If your analysis uncovers a third-party component that you rely on, you can contact the provider and let them know of the upcoming changes. You can then either work with the provider to get an updated library that won't rely on Internal APIs, or you can find an alternative provider for the capabilities that the offending library provides.

Dynamic use of Internal APIs:
JDeps can not detect dynamic use of internal APIs, for example through reflection, service loaders and similar mechanisms.

Rgds,Rory

[0] https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland
Clebert Suconic | 30 Jun 16:08 2015
Picon

jms 2.0 spec jar

Is it possible someone make a cut of the JMS 2.0 spec jar?

We need a new release cut to fix this version:
https://issues.apache.org/jira/browse/ARTEMIS-148

vishnu (JIRA | 28 Jun 05:31 2015
Picon

[jira] [Commented] (GERONIMO-4576) Make persistence exceptions more visible to client


    [
https://issues.apache.org/jira/browse/GERONIMO-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604498#comment-14604498
] 

vishnu commented on GERONIMO-4576:
----------------------------------

i have checked the geronimo-transaction-3.1.2 and geronimo-transaction-3.1.3 jars for the patch 

GERONIMO-4576-1.patch[ 12684899 ] in TransactionImpl.class , don't see .

By the way which version has this patch.

> Make persistence exceptions more visible to client
> --------------------------------------------------
>
>                 Key: GERONIMO-4576
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4576
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: persistence
>    Affects Versions: 2.2
>         Environment: Linux, Windows
>            Reporter: Joe Bohn
>            Priority: Minor
>             Fix For: Wish List
>
>         Attachments: GERONIMO-4576-1.patch
>
>
> See http://issues.apache.org/jira/browse/GERONIMO-3907  for details of the original problem.   That
core problem was resolved.  However, upon resolution it was mentioned that it would be beneficial to
report more specific failure information back to the client.  From GERONIMO-3907:
> Ralf Baumhof - 06/May/08 06:17 AM
> Today if have tested the new Geronimo release 2.1.1 (published on 28.04.2008). The problem is now fixed.
If the server gets an error on trying a commit, this error is now thrown to the web bean.
> Exception text:
> javax.ejb.EJBTransactionRolledbackException: Transaction was rolled back, presumably because
setRollbackOnly was called during a synchronization: Unable to commit: transaction marked for
rollback Root Cause: javax.transaction.TransactionRolledbackException : Transaction was rolled
back, presumably because setRollbackOnly was called during a synchronization: Unable to commit:
transaction marked for rollback
> Unfortunately there is no proper root cause attached to the exception. So the cause can only be seen in the
server console, but can not be reported to the user. It would be very nice if you could change this in a later release.
> Thanks for your help.
> Vincent MATHON - 06/Nov/08 02:03 AM
> I agree that exceptions on the server side should not be thrown to the client side since such exceptions
types might not be known by the client. However, for unit testing purpose, it is useful to attach the root
cause to the RollBackException. I have modified a few lines in
org.apache.geronimo.transaction.manager.TransactionImpl.java to attach the root cause in case of
RollBackException and it works for my unit testing purpose (I have not enough background on the java
transaction architecture topic to submit a patch for production). It would be great to define a
configuration parameter that permits to provide the root cause to the client and keep the current
behaviour that does not by default.
> Geoff Callender - 22/Dec/08 03:36 AM
> It's useful for more than unit testing - it's essential to be able to inform the client what's wrong with the
request. I've added some examples of this to https://issues.apache.org/jira/browse/OPENEJB-782 .

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Gmane