Ok, I added a remote tag and I started trying to deploy, but it
keeps trying to deploy my ejb jar, instead of my ear.
com.baselogic.yoursos
ear
ear
OK, here is my plugin now:
org.codehaus.cargo
cargo-maven2-plugin
0.3-SNAPSHOT
jboss4x
C:/jb
Hi,
all seems ok...
1) please give the console error...
2) did u try to uncomment
$\{project.build.directory\
}/$\{project.build.finalName\}.$\{project.packaging\}
specifying the parameters needed?
Regards
Daniele
On 10/25/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
>
> Well, this seems ha
Well, this seems harder than I thought.
I have a dev machine with JBoss 4.2.1.GA installed and configured already at
c:/jboss-4.2.1.GA/ and I use this plugin:
org.codehaus.cargo
cargo-maven2-plugin
0.3-SNAPSHOT
Hi,
I'm sorry for replying so shortly, but you could see i.e.
http://www.nabble.com/JBoss-Remote-Deployment-workaround-for-HTTP-500-error-t3607694.html
just for the pom
Besides of course, you could refer to
http://cargo.codehaus.org/JBoss+4.x
Just google a little... ;-)
Regards
Daniel
Hi,
do you have a pom example for starting an existing jboss 4.2.0 with cargo?
Thanks,
Catalin
On 10/25/07, Daniele De Francesco <[EMAIL PROTECTED]> wrote:
>
> Hi,
> try using maven cargo plugin instead of the maven-jboss-plugin
>
> *http://cargo*.codehaus.org/*Maven*2+*plugin*
>
> and for
Hi,
try using maven cargo plugin instead of the maven-jboss-plugin
*http://cargo*.codehaus.org/*Maven*2+*plugin*
and for a necessary download and overview about what cargo is... surprise
surprise :)
*http://cargo*.codehaus.org
let me know...
Daniele
On 10/23/07, Mick Knutson <[EMAIL PROTE
btw, if I start jboss manually, then run the build, the application gets
deployed fine.
On 10/23/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
>
> I have the following declaration for jboss:
>
>
> org.codehaus.mojo
> jboss-maven-plugin
>
I have the following declaration for jboss:
org.codehaus.mojo
jboss-maven-plugin
${env.JBOSS_HOME}
8080
start-server
