This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 241362 - Unable to deploy Maven WAR to Elastic Beanstalk
Summary: Unable to deploy Maven WAR to Elastic Beanstalk
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Maven (show other bugs)
Version: 8.0
Hardware: PC Other
: P3 normal (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-04 03:51 UTC by djc391
Modified: 2016-07-07 08:54 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description djc391 2014-02-04 03:51:08 UTC
I have been using Netbeans 7.4 with no issue.

I created a new Maven Web Application. I have entered my AWS Elastic Beanstalk info, and can see my envs listed under servers. 

When I select to run on my Elastic Beanstalk I get the following warning. 

"The target server does not support debuggin. Choose a different server in project properties. 

No change in project, deploys fine in 7.4.
Comment 1 Martin Entlicher 2014-02-04 07:57:13 UTC
It should not require any debugging on run...
Comment 2 Martin Janicek 2014-02-04 09:17:31 UTC
Sounds like Maven issue. Reporter (or Davide) is there any way how could I use AWS Elastic Beanstalk without entering my credit card details ?

The problem might be that since NetBeans 8.0 we are checking if the server on which you are trying to profile/debug application supports this action or not.

That means:
- If you are running application it should definitely not shown this message and I just need to know how to setup AWS Elastic Beanstalk
- If you are debugging/profiling application, is it possible that AWS Elastic Beanstalk doesn't support these actions?
Comment 3 djc391 2014-02-04 16:01:00 UTC
I will confirm that I am not running in debug/profiling mode

I am just selecting Run.

I do not believe you would be able to create an AWS account with a credit card, but you can run things(NOT SURE about EBS) on "micro" instances for free.
Comment 4 djc391 2014-02-04 16:01:38 UTC
*without a credit card
(In reply to djc391 from comment #3)
> I will confirm that I am not running in debug/profiling mode
> 
> I am just selecting Run.
> 
> I do not believe you would be able to create an AWS account with a credit
> card, but you can run things(NOT SURE about EBS) on "micro" instances for
> free.
Comment 5 Martin Janicek 2014-02-17 12:44:53 UTC
(In reply to djc391 from comment #3)
> I do not believe you would be able to create an AWS account with a credit
> card, but you can run things(NOT SURE about EBS) on "micro" instances for
> free.

Unfortunately EBS is not available on micro instances :-/ ..I'll try to find someone with AWS account
Comment 6 djc391 2014-02-17 14:01:50 UTC
I am reaching out to my AWS customer rep and seeing if I can find a contact for you about getting an AWS credit for this dev purpose.
Comment 7 Martin Janicek 2014-02-17 14:07:35 UTC
Sounds cool, I need only day or two (outside of weekend :P) access or something like that. The issue shouldn't be complicated to fix and I think I know about location of this problem, just need to debug the code. Let me know if you get to something. Thanks!
Comment 8 djc391 2014-02-17 16:27:31 UTC
This might be able to help

"Have him go to https://aws.amazon.com/contact-us/ and click on the Billing and Account inquires link and provide details on the bug he hit and specifics of the credit he is looking for. Our customer service team should be able to help."
Comment 9 Martin Janicek 2014-02-18 09:33:31 UTC
Unfortunately I can't click on any kind of link under "Billing and Account inquires" because it forced me to sign-up first which again means to give them credit card details :-/
Comment 10 David Konecny 2014-02-18 20:17:48 UTC
Yeah, the credit card is needed. It will not cost you anything if you run single testing instance only and switch it off after you are finished with it.
Comment 11 Martin Balin 2016-07-07 08:54:28 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss