-
1. Re: This project cannot be deployed to a server.
maxandersen Aug 3, 2006 8:14 AM (in response to mvilot)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 Aug 3, 2006 8:42 AM (in response to mvilot)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 Aug 3, 2006 9:07 AM (in response to 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 Aug 3, 2006 9:07 AM (in response to 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 Aug 3, 2006 9:10 AM (in response to mvilot)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 Aug 3, 2006 9:33 AM (in response to mvilot)>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 Aug 4, 2006 8:26 AM (in response to 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 Aug 4, 2006 9:12 AM (in response to mvilot)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 Aug 7, 2006 12:39 PM (in response to 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 Aug 7, 2006 12:41 PM (in response to mvilot)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 Aug 9, 2006 4:17 PM (in response to 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.
mculpepper Aug 9, 2006 4:43 PM (in response to mvilot)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 Aug 14, 2006 8:49 AM (in response to 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 Aug 14, 2006 9:12 AM (in response to mvilot)the alpha version works for me, but if you want the old behavior use 1.6 on eclipse 3.1