Question on if a bug will ever be looked at and how to proceed

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Question on if a bug will ever be looked at and how to proceed

Brett Bergquist
I opened 


And 


But received this email:

This is an automatically generated Delivery Status Notification.Final-Recipient: rfc822;<[hidden email]>
Diagnostic-Code: 550 Requested action not taken: mailbox unavailable
Action: failed
Status: 5.0.0


Subject: [Bug 271314] Unable to deploy EAR with additional WAR or EBJ module that is not a project of the EAR with ANT project
Date: August 16, 2017 at 11:06:03 PM EDT



brett <[hidden email]> changed:

          What    |Removed                     |Added
----------------------------------------------------------------------------
          See Also|                            |https://netbeans.org/bugzil
                  |                            |la/show_bug.cgi?id=271216

--- Comment #1 from brett <[hidden email]> ---
See bug#271216 that I wrote about providing the ability to force archive
deployment.  I don't think this should be the final solution as one completely
loses the benefits of directory deployment.

-- 
You are receiving this mail because:
You are the assignee for the bug.

So it appears that the “Assigned to” person is no longer receiving the emails.   Bug #271314 is pretty severe in that if you build an EAR and it contains modules that are added that are prebuilt outside of NetBeans, you can never deploy the EAR from within NetBeans as NetBeans always tries to do directory deployment and this fails because the expansion of the contained modules is not supported if these modules are referenced as NetBeans projects (WAR or EJB).

I will attach a patch or bug#271216 which provides support for marking the Glassfish server being deployed to as forcing archive deployment.

I am wondering if these bugs will ever be looked at by someone else.   I have done some investigation on the first bug but don’t see a simple solution at this point.  


Reply | Threaded
Open this post in threaded view
|

Re: Question on if a bug will ever be looked at and how to proceed

geertjan.wielenga@oracle.com
Hey Brett,

We’re kind of in a transitional state at the moment, in the process of moving to Apache. Once there, yes, everything like this will be done, assigned to people, etc. There’s also the Apache NetBeans bug tracker that you could be pointed to, but best to wait until the code is actually there. Anyway, hang in there for the moment, and be aware we’ll get back to this as soon as we can.

Gj

On 17 Aug 2017, at 13:33, Brett Bergquist <[hidden email]> wrote:

I opened 


And 


But received this email:

This is an automatically generated Delivery Status Notification.Final-Recipient: rfc822;<[hidden email]>
Diagnostic-Code: 550 Requested action not taken: mailbox unavailable
Action: failed
Status: 5.0.0


Subject: [Bug 271314] Unable to deploy EAR with additional WAR or EBJ module that is not a project of the EAR with ANT project
Date: August 16, 2017 at 11:06:03 PM EDT



brett <[hidden email]> changed:

          What    |Removed                     |Added
----------------------------------------------------------------------------
          See Also|                            |https://netbeans.org/bugzil
                  |                            |la/show_bug.cgi?id=271216

--- Comment #1 from brett <[hidden email]> ---
See bug#271216 that I wrote about providing the ability to force archive
deployment.  I don't think this should be the final solution as one completely
loses the benefits of directory deployment.

-- 
You are receiving this mail because:
You are the assignee for the bug.

So it appears that the “Assigned to” person is no longer receiving the emails.   Bug #271314 is pretty severe in that if you build an EAR and it contains modules that are added that are prebuilt outside of NetBeans, you can never deploy the EAR from within NetBeans as NetBeans always tries to do directory deployment and this fails because the expansion of the contained modules is not supported if these modules are referenced as NetBeans projects (WAR or EJB).

I will attach a patch or bug#271216 which provides support for marking the Glassfish server being deployed to as forcing archive deployment.

I am wondering if these bugs will ever be looked at by someone else.   I have done some investigation on the first bug but don’t see a simple solution at this point.