[jbosstools-dev] Maven Publishing Goals on Server Edit

Rob Stryker rob.stryker at redhat.com
Mon Aug 10 16:48:14 EDT 2009


Howdy ;)

If you see an "Ant Publishing" section, it means you are not creating a 
JBoss Tools server, but you *are* making a webtools server.  The 
JBossTools servers do not have "Ant Publishing" listed in our server 
editor =]

When trying to create a new server, you'll see three sections:
 1) JBoss
 2) JBoss Community
 3) JBoss Enterprise Middleware

Only Server types 2) and 3) are made by us. Server type one is 
automatically provided by webtools.

Currently we only do direct file-system coppies for the most part. We 
don't support ant publishing (way too slow, launches separate vm, etc) 
or remote deployment just yet. I've been trying to think of a way to 
allow such things but haven't come to a conclusion yet on the best way 
to architect it. Currently several different module types have their own 
"publisher" which still only does a local file publish. I've been 
struggling to imagine a UI that can allow the user to customize each 
available module's publisher and details.

My current idea was just to allow each module override our default 
behaviour. In case you're not familiar, our default behaviour is to 
publish to one of three places: in the server's deploy folder, in the 
jbosstools plugin metadata location, or in a custom folder somewhere 
else on the hard drive. So this would allow the user to designate where 
each module would go. Since there are only two variables in this example 
(type, and location), it could easily be represented in a 3-column grid.

But once you start talking about different TYPES of deployers (ssh, 
maven, ant) it starts opening up an array of different-sized 
requirements. An ant publisher would require a file, a target, a base 
directory, etc. A maven publisher would require, I don't even know what. 
An SSH publisher would require server, port, username, password, root 
folder to publish to, etc.

I see no easy way to represent these in a server editor section. However 
I can add a server editor PAGE (the server editor is a multi-page 
editor). But I've still been having problems drafting a UI for it.

Daniel Green wrote:
> Hello!
>
> It would be cool if the user, on the server edit page, could specify
> maven goals to be used for generating the ear or war file to be
> published. Right under the "Ant Publisher Properties" there's some
> room... Is this a feasible goal? I'd be willing to put time into
> developing it. As of now, deploying has been a gigantic pain when
> using maven. I've found myself fighting with eclipse for days now...
> Obviously not all projects would be maven enabled, so perhaps checking
> for m2eclipse nature or a pom.xm before building that way. The latter
> may be best. How feasible is this?
>
> Thank you for hearing my idea,
> Daniel.
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>   



More information about the jbosstools-dev mailing list