> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, June 16, 2003 8:54 PM > To: 'Maven Developers List' > Subject: RE: JBoss plugin - new modifications > > > > > > -----Original Message----- > > From: Michal Maczka [mailto:[EMAIL PROTECTED] > > Sent: 16 June 2003 19:14 > > To: Maven Developers List > > Subject: RE: JBoss plugin - new modifications > > > > > > > > > -----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> > > > <groupId>everest</groupId> > > > <artifactId>registration</artifactId> > > > <version>1.0-SNAPSHOT</version> > > > <type>ear</type> > > > <properties> > > > <jboss.bundle>true</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? > > There is no reason all dependencies should be bundled. Only those that > are supposed to be deployed in JBoss. For example, on a project at work, > we get the JBoss install from the repository and we have a pregoal to > unzip it and feed it to the jboss plugin. > > >
What are you going to do exactly if you are going to have (just e.g) separte ejb and jboss plugins? Are you going to update ejb jar archive? Befor asking this question I though Is't you project layout going to look like: -jboss1 -jboss2 -jbossK -ejb1 -ejb2 ... -ejbN -war1 -war2 ... -warM -ear1 -ear2 -earK -earK But now I get lost and not sure what you are going to do What for do you need other dependencies? Can you just give an exaple what you are going to achieve? > > 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.port }/jmx-console/HtmlAdaptor?action=invokeOp&name=jboss.system:service%3DMainDe ployer&methodIndex=19&arg0= maven.jboss.jmx.url.undeploy=http://${maven.jboss.hostname}:${maven.jboss.po rt}/jmx-console/HtmlAdaptor?action=invokeOp&name=jboss.system:service%3DMain Deployer&methodIndex=2&arg0= Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
