jboss 4 and Cargo maven 1 plugin

[AlexeySem]

Hi All,

I am currently organizing a continuous integration for a fairly old project, which is currently built using Maven 1.1 and then deployed to JBoss 4.0.5. We decided to try Hudson, and Cactus 1.8.1 + Cargo 0.9 for testing and deploying.

So here's the summary of my configuration:
- Maven 1.1
- Cactus 1.8.1 Maven 1 plugin
- Cargo 0.9 ant task used by Cactus
- JBoss 4.0.5

However, accordingly the documentation at http://cargo.codehaus.org/JBoss+4.x currently Cargo Ant plugin only supports local standalone jboss installations, and it is Cargo Maven 2 plugin which supports the installed and remote installations - the two that I actually need.

Please tell, is that correct? I guess that from all Ant, Maven 1 and Maven 2 plugins there comes similar information - properties and settings, so why so prominent difference in functionality? How could I deploy to JBoss 4.0.5 with Cargo 0.9 and start/stop the container - maybe there's a known workaround, or a solution without Cargo?

I've also found a Maven 1 JBoss plugin, but it seems to be deprecated and abandoned.

Any help appreciated.

Thanks in advance,
Alexey

[Matt Wringe]

On Wed, 2009-06-03 at 16:11 +0100, Alexey Semenov wrote:

> Hi All,
>
> I am currently organizing a continuous integration for a fairly old
> project, which is currently built using Maven 1.1 and then deployed to
> JBoss 4.0.5. We decided to try Hudson, and Cactus 1.8.1 + Cargo 0.9
> for testing and deploying.
>
> So here's the summary of my configuration:
> - Maven 1.1
> - Cactus 1.8.1 Maven 1 plugin
> - Cargo 0.9 ant task used by Cactus
> - JBoss 4.0.5
>
> However, accordingly the documentation at
> http://cargo.codehaus.org/JBoss+4.x currently Cargo Ant plugin only
> supports local standalone jboss installations, and it is Cargo Maven 2
> plugin which supports the installed and remote installations - the two
> that I actually need.

The plugins for Cargo are usually just wrapper around the main Cargo
core. I am not sure why it says its not supported in Ant (it should
work), I will look into it and see what the issue is.

> Please tell, is that correct? I guess that from all Ant, Maven 1 and
> Maven 2 plugins there comes similar information - properties and
> settings, so why so prominent difference in functionality? How could I
> deploy to JBoss 4.0.5 with Cargo 0.9 and start/stop the container -
> maybe there's a known workaround, or a solution without Cargo?
>
> I've also found a Maven 1 JBoss plugin, but it seems to be deprecated
> and abandoned.

The maven 1 plugin hasn't had a lot of interest lately and might have a
few issues. We need someone to start working on Cargo that will take up
this task.

> Any help appreciated.
>
> Thanks in advance,
> Alexey
>


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[AlexeySem]

Hi Matt,

Thanks for your response, looking forward to the results of your investigation. The difference in functionality between the maven1, maven2 and ant plugins is surprising for me; however, I have only glanced at the code yet.

I have to stick to maven1 as it looks like updating all the system to use maven2 will take days and maybe even weeks...

Thanks,
Alexey

On Thu, Jun 4, 2009 at 3:26 PM, Matt Wringe <mwringe@...> wrote:

On Wed, 2009-06-03 at 16:11 +0100, Alexey Semenov wrote:
> Hi All,
>
> I am currently organizing a continuous integration for a fairly old
> project, which is currently built using Maven 1.1 and then deployed to
> JBoss 4.0.5. We decided to try Hudson, and Cactus 1.8.1 + Cargo 0.9
> for testing and deploying.
>
> So here's the summary of my configuration:
> - Maven 1.1
> - Cactus 1.8.1 Maven 1 plugin
> - Cargo 0.9 ant task used by Cactus
> - JBoss 4.0.5
>
> However, accordingly the documentation at
> http://cargo.codehaus.org/JBoss+4.x currently Cargo Ant plugin only
> supports local standalone jboss installations, and it is Cargo Maven 2
> plugin which supports the installed and remote installations - the two
> that I actually need.

The plugins for Cargo are usually just wrapper around the main Cargo
core. I am not sure why it says its not supported in Ant (it should
work), I will look into it and see what the issue is. 

> Please tell, is that correct? I guess that from all Ant, Maven 1 and
> Maven 2 plugins there comes similar information - properties and
> settings, so why so prominent difference in functionality? How could I
> deploy to JBoss 4.0.5 with Cargo 0.9 and start/stop the container -
> maybe there's a known workaround, or a solution without Cargo?
>
> I've also found a Maven 1 JBoss plugin, but it seems to be deprecated
> and abandoned.

The maven 1 plugin hasn't had a lot of interest lately and might have a
few issues. We need someone to start working on Cargo that will take up
this task.

> Any help appreciated.
>
> Thanks in advance,
> Alexey
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Matt Wringe]

On Thu, 2009-06-04 at 15:37 +0100, Alexey Semenov wrote:
> Hi Matt,
>
> Thanks for your response, looking forward to the results of your
> investigation. The difference in functionality between the maven1,
> maven2 and ant plugins is surprising for me; however, I have only
> glanced at the code yet.

I have a feeling its there isn't a difference in functionality for the
most part. I suspect that whatever data is being used to generate that
page is wrong.

>
> I have to stick to maven1 as it looks like updating all the system to
> use maven2 will take days and maybe even weeks...
>
> Thanks,
> Alexey
>
> On Thu, Jun 4, 2009 at 3:26 PM, Matt Wringe <mwringe@...>
> wrote:
>         On Wed, 2009-06-03 at 16:11 +0100, Alexey Semenov wrote:
>         > Hi All,
>         >
>         > I am currently organizing a continuous integration for a
>         fairly old
>         > project, which is currently built using Maven 1.1 and then
>         deployed to
>         > JBoss 4.0.5. We decided to try Hudson, and Cactus 1.8.1 +
>         Cargo 0.9
>         > for testing and deploying.
>         >
>         > So here's the summary of my configuration:
>         > - Maven 1.1
>         > - Cactus 1.8.1 Maven 1 plugin
>         > - Cargo 0.9 ant task used by Cactus
>         > - JBoss 4.0.5
>         >
>         > However, accordingly the documentation at
>         > http://cargo.codehaus.org/JBoss+4.x currently Cargo Ant
>         plugin only
>         > supports local standalone jboss installations, and it is
>         Cargo Maven 2
>         > plugin which supports the installed and remote installations
>         - the two
>         > that I actually need.
>        
>        
>         The plugins for Cargo are usually just wrapper around the main
>         Cargo
>         core. I am not sure why it says its not supported in Ant (it
>         should
>         work), I will look into it and see what the issue is.
>        
>        
>         > Please tell, is that correct? I guess that from all Ant,
>         Maven 1 and
>         > Maven 2 plugins there comes similar information - properties
>         and
>         > settings, so why so prominent difference in functionality?
>         How could I
>         > deploy to JBoss 4.0.5 with Cargo 0.9 and start/stop the
>         container -
>         > maybe there's a known workaround, or a solution without
>         Cargo?
>         >
>         > I've also found a Maven 1 JBoss plugin, but it seems to be
>         deprecated
>         > and abandoned.
>        
>        
>         The maven 1 plugin hasn't had a lot of interest lately and
>         might have a
>         few issues. We need someone to start working on Cargo that
>         will take up
>         this task.
>        
>         > Any help appreciated.
>         >
>         > Thanks in advance,
>         > Alexey
>         >
>        
>        
>        
>         ---------------------------------------------------------------------
>         To unsubscribe from this list, please visit:
>        
>            http://xircles.codehaus.org/manage_email
>        
>        
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[AlexeySem]

But still, I didn't manage to make Cargo Maven1 run the container in an installed mode... Though, in fact I tried it only inside Cactus 1.8.1, which's a buggy thing itself.

On Thu, Jun 4, 2009 at 3:40 PM, Matt Wringe <mwringe@...> wrote:

On Thu, 2009-06-04 at 15:37 +0100, Alexey Semenov wrote:
> Hi Matt,
>
> Thanks for your response, looking forward to the results of your
> investigation. The difference in functionality between the maven1,
> maven2 and ant plugins is surprising for me; however, I have only
> glanced at the code yet.

I have a feeling its there isn't a difference in functionality for the
most part. I suspect that whatever data is being used to generate that
page is wrong.

>
> I have to stick to maven1 as it looks like updating all the system to
> use maven2 will take days and maybe even weeks...
>
> Thanks,
> Alexey
>
> On Thu, Jun 4, 2009 at 3:26 PM, Matt Wringe <mwringe@...>
> wrote:
>         On Wed, 2009-06-03 at 16:11 +0100, Alexey Semenov wrote:
>         > Hi All,
>         >
>         > I am currently organizing a continuous integration for a
>         fairly old
>         > project, which is currently built using Maven 1.1 and then
>         deployed to
>         > JBoss 4.0.5. We decided to try Hudson, and Cactus 1.8.1 +
>         Cargo 0.9
>         > for testing and deploying.
>         >
>         > So here's the summary of my configuration:
>         > - Maven 1.1
>         > - Cactus 1.8.1 Maven 1 plugin
>         > - Cargo 0.9 ant task used by Cactus
>         > - JBoss 4.0.5
>         >
>         > However, accordingly the documentation at
>         > http://cargo.codehaus.org/JBoss+4.x currently Cargo Ant
>         plugin only
>         > supports local standalone jboss installations, and it is
>         Cargo Maven 2
>         > plugin which supports the installed and remote installations
>         - the two
>         > that I actually need.
>
>
>         The plugins for Cargo are usually just wrapper around the main
>         Cargo
>         core. I am not sure why it says its not supported in Ant (it
>         should
>         work), I will look into it and see what the issue is.
>
>
>         > Please tell, is that correct? I guess that from all Ant,
>         Maven 1 and
>         > Maven 2 plugins there comes similar information - properties
>         and
>         > settings, so why so prominent difference in functionality?
>         How could I
>         > deploy to JBoss 4.0.5 with Cargo 0.9 and start/stop the
>         container -
>         > maybe there's a known workaround, or a solution without
>         Cargo?
>         >
>         > I've also found a Maven 1 JBoss plugin, but it seems to be
>         deprecated
>         > and abandoned.
>
>
>         The maven 1 plugin hasn't had a lot of interest lately and
>         might have a
>         few issues. We need someone to start working on Cargo that
>         will take up
>         this task.
>
>         > Any help appreciated.
>         >
>         > Thanks in advance,
>         > Alexey
>         >
>
>
>
>         ---------------------------------------------------------------------
>         To unsubscribe from this list, please visit:
>
>            http://xircles.codehaus.org/manage_email
>
>
>


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email