14 Replies Latest reply on Aug 14, 2006 9:12 AM by maxandersen

    This project cannot be deployed to a server.

    mvilot

      The one feature I need from JBoss IDE is convenient deployment of J2EE components. However, it's the one feature that's broken. Where's QA on this?

      Configuration:
      - Windoze XP Pro SP 2
      - Java 1.5.0_07
      - JBossAS 4.0.4 GA patch 1
      - JBoss IDE 2.0.0 alpha 1a

      After creating a J2EE 1.4 project and running XDoclet to generate the needed descriptors, unable to deploy.

      For Project -> Properties -> Server, dialog box says "This project cannot be deployed to a server."

      For Run -> Debug (?!?!) -> no JBoss server configuration appears.

      However, for New -> Server, a JBoss 4 server option appears, can be configured, and can be run/stopped from Eclipse. Unfortunately, the J2EE part of JBoss IDE does not recognize it at all.

      This all seemed to work for Java 1.4. Unfortunately, my project needs the latest Java features.

      When will a fix be available?

        • 1. Re: This project cannot be deployed to a server.
          maxandersen

          not to be picky, but it *is* an alpha version.

          But yes, there seem to be a bug so go and report it in jira with enough details and it will be taken care of.

          • 2. Re: This project cannot be deployed to a server.
            rob.stryker

            Hi.

            Are you using the jboss IDE packaging utilities to package your project into a jar / war/ ear / sar / etc?

            To easily deploy any jar-style archive, simply right-click on the generated jar file, select run as -> run on server. A dialog will ask you which server to run on, and you should select the created jboss server. This should quickly deploy the file to the jboss server.

            As a word of warning, the packaging utilities will also be new by the time 2.0 becomes a full release.

            • 3. Re: This project cannot be deployed to a server.
              mvilot

               

              "max.andersen@jboss.com" wrote:
              not to be picky, but it *is* an alpha version.

              But yes, there seem to be a bug so go and report it in jira with enough details and it will be taken care of.



              Yes, I understand the alpha quality of *new* features. However, is it unreasonable to expect no regression on *existing* features?

              If I wanted to alpha-test released softtware, I'd stick with Micro$oft :-(


              • 4. Re: This project cannot be deployed to a server.
                mvilot

                 

                "rob.stryker@jboss.com" wrote:
                Hi.

                Are you using the jboss IDE packaging utilities to package your project into a jar / war/ ear / sar / etc?

                To easily deploy any jar-style archive, simply right-click on the generated jar file, select run as -> run on server. A dialog will ask you which server to run on, and you should select the created jboss server. This should quickly deploy the file to the jboss server.

                As a word of warning, the packaging utilities will also be new by the time 2.0 becomes a full release.


                Yes, the packaging works. It's the deployment that's broken.


                • 5. Re: This project cannot be deployed to a server.
                  rob.stryker

                  What, exactly, is the error you are getting?

                  The process, again, is right-click on the .jar / .ear / whatever, and select run as -> run on server. Then select the created server.

                  • 6. Re: This project cannot be deployed to a server.
                    maxandersen

                    >If I wanted to alpha-test released softtware, I'd >stick with Micro$oft :-(

                    Then don't download *alpha* releases, but only stick with full final releases.

                    But your feeback is appreciated; just don't expect more of the release than what it is called.

                    • 7. Re: This project cannot be deployed to a server.
                      mvilot

                       

                      "max.andersen@jboss.com" wrote:
                      >If I wanted to alpha-test released softtware, I'd >stick with Micro$oft :-(

                      Then don't download *alpha* releases, but only stick with full final releases.

                      But your feeback is appreciated; just don't expect more of the release than what it is called.



                      Well, then, here's some more feedback: why don't you separate the components into focused plugins, and coordinate their distribution via Callisto?

                      That way, we don't have a proliferation of different IDEs "Based on" Eclipse.

                      And, hopefully, core features (such as deployment to the app server) will remain stable for longer periods.

                      • 8. Re: This project cannot be deployed to a server.
                        maxandersen

                        Dude ;)

                        "why don't you separate the components into focused plugins, and coordinate their distribution via Callisto?"

                        Is that not what we are actually doing ?!

                        We got about 6-7 different plugins for each major functionallity and targetting Callisto have been the goal ever since it became stable/available.

                        • 9. Re: This project cannot be deployed to a server.
                          mvilot

                           

                          "max.andersen@jboss.com" wrote:
                          Dude ;)

                          "why don't you separate the components into focused plugins, and coordinate their distribution via Callisto?"

                          Is that not what we are actually doing ?!

                          We got about 6-7 different plugins for each major functionallity and targetting Callisto have been the goal ever since it became stable/available.



                          Well, you sure fooled me -- downloading a separate .zip file that contains _all_ of Eclipse doesn't seem like a plugin. No wonder I was confused. Dude.

                          • 10. Re: This project cannot be deployed to a server.
                            maxandersen

                            huh ? What are you talking about ?

                            We have one full eclipse download with all our plugins.

                            All these plugins are downloadable in individual form.

                            /max

                            • 11. Re: This project cannot be deployed to a server.
                              mvilot

                               

                              "max.andersen@jboss.com" wrote:
                              huh ? What are you talking about ?

                              We have one full eclipse download with all our plugins.

                              All these plugins are downloadable in individual form.

                              /max


                              Well, not from http://labs.jboss.com/portal/jbosside/download/index.html

                              From where, then?

                              • 12. Re: This project cannot be deployed to a server.

                                mvilot, as you can see on the link you provided there are 3 different types of downloads:

                                - Bundle downloads (aka Eclipse is bundled)
                                - ALL download (all of our plugins one big zip file, eclipse is NOT bundled)
                                - Single component/plugin downloads. These are *standalone* versions of all the components in JBossIDE. These also include all the necessary dependencies to run in a clean version of eclipse for convenience.

                                • 13. Re: This project cannot be deployed to a server.
                                  mvilot

                                   

                                  "mculpepper@jboss.com" wrote:
                                  mvilot, as you can see on the link you provided there are 3 different types of downloads:

                                  - Bundle downloads (aka Eclipse is bundled)
                                  - ALL download (all of our plugins one big zip file, eclipse is NOT bundled)
                                  - Single component/plugin downloads. These are *standalone* versions of all the components in JBossIDE. These also include all the necessary dependencies to run in a clean version of eclipse for convenience.


                                  OK, great. Now, back to the point that started this thread: which is the most recent version that has deployment to the server working?

                                  • 14. Re: This project cannot be deployed to a server.
                                    maxandersen

                                    the alpha version works for me, but if you want the old behavior use 1.6 on eclipse 3.1