RE: JBoss plugin - new modifications

[Vincent Massol]

 -Original Message-
 From: James CE Johnson [mailto:[EMAIL PROTECTED]
 Sent: 20 June 2003 02:51
 To: Maven Developers List
 Subject: Re: JBoss plugin - new modifications

[snip]

 
 Perhaps there should be a maven.jboss.version property and a j:if tag
 would check that in order to invoke the right JMX thing. I seem to
 recall that the url was something different before we upgraded to
3.0.x...
 
 j:if test=${maven.jboss.version == '3.0.x'}
   the stuff we have now...
 /j:if
 j:if test=${maven.jboss.version == '3.2.x'}
   whatever is appropriate for 3.2.x...
 /j:if
 

Sure. I have now introduced this property but I still don't have the
patch for JMX stuff with 3.2.x. Anyone?

Thanks
-Vincent


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: JBoss plugin - new modifications

[James CE Johnson]

   

BTW: Are you going to make jboss plugin compatible with jboss 3.2x
   

series?

What is not compatible? I seem to remember I have used it with JBoss
3.2.1.
 

   

maven.jboss.jmx.url.deploy=http://${maven.jboss.hostname}:${maven.jboss.
po
 

rt
}/jmx-
console/HtmlAdaptor?action=invokeOpname=jboss.system:service%3DMainDe
ployermethodIndex=19arg0=
   

maven.jboss.jmx.url.undeploy=http://${maven.jboss.hostname}:${maven.jbos
s.
 

po
rt}/jmx-
console/HtmlAdaptor?action=invokeOpname=jboss.system:service%3DMain
DeployermethodIndex=2arg0=
Perhaps there should be a maven.jboss.version property and a j:if tag 
would check that in order to invoke the right JMX thing. I seem to 
recall that the url was something different before we upgraded to 3.0.x...

j:if test=${maven.jboss.version == '3.0.x'}
 the stuff we have now...
/j:if
j:if test=${maven.jboss.version == '3.2.x'}
 whatever is appropriate for 3.2.x...
/j:if
 


   

ok, I haven't used those JMX deployments yet. The rest works with JBoss
3.2.x (the static deployment part).
Would you have a patch for the JMX stuff :-) ?

Thanks
-Vincent


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: JBoss plugin - new modifications

[Michal Maczka]

 -Original Message-
 From: Vincent Massol [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 16, 2003 6:33 PM
 To: 'Maven Developers List'
 Subject: JBoss plugin - new modifications
 
 
 Hi,
 
 I don't like the way the jboss plugin works. ATM, it assumes the EAR and
 the jboss packaging is done in the same project. I think they are 2
 separate activities that should be done in 2 separate projects. Why?
 
 Because packaging something in JBoss can mean packaging several modules:
 An EAR module, an EJB-JAR one, a WAR one, etc. and this won't work in a
 single project.
 
 Proposal:
 
 * Add a jboss.bundle property for dependencies. Example:
 
 dependencies
   dependency
 groupIdeverest/groupId
 artifactIdregistration/artifactId
 version1.0-SNAPSHOT/version
 typeear/type
 properties
   jboss.bundletrue/jboss.bundle
 /properties
   /dependency
 /dependencies
 
 * Keep only a jboss:package goal (remove the jboss:package-ear, etc) as
 they are no longer needed. The modules to package are now listed in the
 dependencies list
 
 If no one has any objection, I'll implement this in the coming 1-2 days.
 
 Thanks
 -Vincent
 
 

Question:
In this project for jboss all dependecies will be bundled, right?
Why to mark them in special way?

BTW: Are you going to make jboss plugin compatible with jboss 3.2x series?

Michal




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]