[JBoss AOP Development] - Feature request for maven aop plugin
by Douglas Palmer
Douglas Palmer [http://community.jboss.org/people/dpalmer%40redhat.com] created the discussion
"Feature request for maven aop plugin"
To view the discussion, visit: http://community.jboss.org/message/567825#567825
--------------------------------------------------------------
Hi
I have been tasked with moving the JBoss ESB build from ant to maven; the current build relies the aopc ant task and the maven aop plugin doesn't seem to be flexible enough. I need to be able to configure which dependencies are included. So my feature request is for an iclude/excludes list for dependencies.
I think I should have the time to implement this in the scope of my current task but I'm sure you guys will have preferences as to how it is implemented. My thoughts are as follows:
1. The includes/excludes options will still require <includeProjectDependencies>true</includeProjectDependencies> and if no includes/excludes are set then all of the dependencies would be added to the classpath.
2. If there are any includes/excludes then a dependency would only be added if it appears in the includes list and it does not appear in the excludes list. Would it suffice to use the artifactId or should the comparison use the full coordinates?
3. Do you have a preference for the name of the elements? I'm leaning towards includedProjectDependencies and excludedProjectDependencies.
Regards
Doug
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/567825#567825]
Start a new discussion in JBoss AOP Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months
[JBoss Internal Benchmarking Development] - Re: Jboss or Glassfish?
by F U
F U [http://community.jboss.org/people/garoad] created the discussion
"Re: Jboss or Glassfish?"
To view the discussion, visit: http://community.jboss.org/message/567785#567785
--------------------------------------------------------------
Sounds like some hogwash Satish. I don't hate JBoss, and I prefer it to just about anything else out there, but you force me to point out the flaws in these talking points which read more like an ad than an honest analysis.
1) JBoss++ may have a bigger and more active community base, but Glassfish appears to be eroding it largely at the expense of JBoss (*and Weblogic*, shocking huh?)
See this link, where it shows Glassfish overtaking JBoss, and *skyrocketing* in popularity.
https://www.sun.com/offers/thankyou/thankyou.xml?id=glassfish_jboss.pdf&o... https://www.sun.com/offers/thankyou/thankyou.xml?id=glassfish_jboss.pdf&o...
*Glassfish was found to be the app server of choice for 73% of new JEE projects according to Ohloh. (WOW!)*
2) ? Like what? And does it really matter? Performance, scalability, usability, and reliability all trump non-standard niche features.
3) Dependence is not as high on Red Hat? Meh, this is a weak one. First, less vendor lock-in is the main benefit of OSS--and both are OSS, so this isn't a major issue even if the dependence is slightly greater. Also, most large conservative corporations would kick you out of the room if you suggested going without support on EITHER JBoss or Glassfish, so either way you're attached to someone. At best this is a modest JBoss win for small shops where they're willing to go without commercial support.
4) Oracle has made it clear that Glassfish is not "going away". And *they couldn't kill it if they wanted* *to at this point*. It would likely just get forked- that's the nice thing about OSS, you should know better than to suggest that Oracle would bury GF just because it +might+ cut into Weblogic's market share. WebSphere is a more likely competitor for Weblogic anyway, not Glassfish. Oracle's not stupid enough to risk losing the cash flow of Glassfish support (by burying it) AND having a forked version (or other competitors) still end up competing with Weblogic in the long run anyway. It's more in their interest to keep supporting it as the replacement to their failed OAS/OC4J junk platform.
5) JBoss is slightly more developed for now, but that era is coming to an end pretty quick. Glassfish is the new favorite JEE server for developers everywhere I look. And GF does very well on benchmarks. JBoss usually does poorly. Perhaps the JBoss code base is starting to suffer from the inevitable bloat that tends to infest software shortly before it starts losing popularity? Or maybe it was just inefficient from the start, who knows. I do know that Glassfish is *fast* based on personal experience as well as benchmarks.
6) Community was already discussed... and apparently JBoss' community is losing ground every year.
7) This is a good point, and I hate super-vendors as much as the next guy, but Oracle has a fairly impressive track record when it comes to competition and they're going to be tough to stop. Not that I want one to "win" over the other--I'd rather have more than one implementation! But Glassfish has the "soul" of Sun Microsystems and it'll probably be some number of years before the usual Oracle bloat ruins that (if it does), but by then at the rate JBoss seems to be going, it'll be even more bloated and aged.
Based on the graphs in the link I posted, Glassfish is stealing the show (and market). Weblogic AND JBoss are on VERY obvious, steady, and long running downward trends which can't be denied in those stats. The IBM scum's overpriced proprietary WebSphere bloatware is flatlined, and will probably remain on life support indefinitely as long as we have moronic corporations that refuse to adopt OSS alternatives simply because it's OSS.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/567785#567785]
Start a new discussion in JBoss Internal Benchmarking Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months
[JBoss Tools Development] - JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools)
by Nick Boldt
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document:
"JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools)"
To view the document, visit: http://community.jboss.org/docs/DOC-15755
--------------------------------------------------------------
*+This document is a work in progress and subject to change.+*
In order to build JBoss Tools in your workspace (or on your local machine, if not in Eclipse), you need to have its dependencies available. There are a number of ways to accomplish this, depending on your needs and how much manual effort you'd like to expend.
First, you'll need the JBoss Tools sources on disk. Fetch sources from trunk (or another branch) into ~/tru (or another location on disk).
svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/ http://anonsvn.jboss.org/repos/jbosstools/trunk/ ~/tru
Next, you can either install the target platform update site into your Eclipse install, or simply let Tycho fetch all the dependencies into a local m2 cached repository.
*------------------------------*
*
*
*OPTION 1: Install Target Platform Update Site into Eclipse*
Point the latest Eclipse 3.6.x build at the http://download.jboss.org/jbosstools/updates/target-platform/latest/ Target Platform update site (generated from this http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/e36... e361-wtp322.target file). Be sure to show uncategorized features, then install everything.
http://download.jboss.org/jbosstools/updates/target-platform/latest/ http://download.jboss.org/jbosstools/updates/target-platform/latest/
After restarting Eclipse, you should have all the dependencies installed to develop JBoss Tools; however, if you want to use this Eclipse as the target platform against which to build using Tycho, you need to also unzip the latest http://http//download.eclipse.org/eclipse/downloads/drops/R-3.6.1-2010090... deltapack (eg., eclipse-M20101020-0925-delta-pack.zip) into your Eclipse root folder. Once you've done that, you can use the following commands to tell Maven (and Tycho) to use that Eclipse instead of doing its own resolution.
You will of course need http://maven.apache.org/download.html Maven 3 installed.
a) Build parent + target platform poms (should only take a few mins; includes 18M of downloaded artifacts into your local Maven cache, eg., ~/.m2).
cd ~/tru/build; mvn3 clean install -f http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml parent/pom.xml
b) Build all components or use the bootstrap profiles in http://anonsvn.jboss.org/repos/jbosstools/trunk/build/pom.xml build/pom.xml to build a stack of components, such as Seam:
cd ~/tru/build; mvn3 clean install +-U -B -e -fae -Dmaven.test.skip+ *-Dtycho.targetPlatform=/path/to/your/eclipse*
*or*
cd ~/tru/build; mvn3 clean install +-U -B -e -fae -Dmaven.test.skip+* -Dtycho.targetPlatform=/path/to/your/eclipse* *+-P seam-bootstrap+*
Note that if you install http://m2eclipse.sonatype.org/ m2eclipse, you can also start mvn3 builds from within Eclipse.
*------------------------------*
*
*
*OPTION 2: Let Tycho Resolve Dependencies From Remote Repo Into Local Cache
*
In this case, you don't even need Eclipse installed - you just need the sources on disk.
You will of course need http://maven.apache.org/download.html Maven 3 installed.
a) Build parent + target platform poms (should only take a few mins; includes 18M of downloaded artifacts into your local Maven cache, eg., ~/.m2).
cd ~/tru/build; mvn3 clean install -f http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml parent/pom.xml
b) Build one or more components (when done, ~/.m2 will be 1.1G in size):
cd ~/tru/build; mvn3 clean install +-U -B -e -fae -Dmaven.test.skip+ *-P \!helios,helios-remote-target*
*or*
cd ~/tru/build; mvn3 clean install +-U -B -e -fae -Dmaven.test.skip+** *-P \!helios,helios-remote-target* *+-P seam-bootstrap+*
The 'helios-remote-target' will fetch all dependencies from this update site:
http://download.jboss.org/jbosstools/updates/target-platform/latest/ http://download.jboss.org/jbosstools/updates/target-platform/latest/
*------------------------------*
*
*
*OPTION 3: Let Tycho Resolve Dependencies From Local Repo Into Local Cache*
*
*
** If have a local Target Platform repo already mirrored on disk (for example, you http://download.jboss.org/jbosstools/updates/target-platform/ downloaded a zip of the above update site and unpacked it somewhere, you can use the 'helios-local-target' profile.
You will of course need http://maven.apache.org/download.html Maven 3 installed.
a) Edit the http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml parent/pom.xml to point to the correct path on disk, and rebuild it. (The default path is the one that Hudson uses.)
vi parent/pom.xml # search for 'helios-local-target'
mvn3 clean install -f parent/pom.xml
b) Build using the 'helios-local-target' profile you modified to point to the correct location on your disk.
cd ~/tru/build; mvn3 clean install +-U -B -e -fae -Dmaven.test.skip+ *-P \!helios,helios-local-target *
*or+
+*
cd ~/tru/build; mvn3 clean install +-U -B -e -fae -Dmaven.test.skip+ *-P \!helios,helios-local-target +-P seam-bootstrap+*
This is how the Hudson builds run: compile the parent & target platform pom.xml files, then build the desired component(s) against a locally available update site.
*------------------------------*
Note that if you install http://m2eclipse.sonatype.org/ m2eclipse, you can also start mvn3 builds from within Eclipse.
For other ways to build, see http://community.jboss.org/docs/DOC-15513 http://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15755]
Create a new document in JBoss Tools Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 2 months
[JBoss Tools Development] - JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools)
by Nick Boldt
Nick Boldt [http://community.jboss.org/people/nickboldt] modified the document:
"JBoss Tools Target Platform Provisioning (or, how to resolve missing dependencies when compiling JBoss Tools)"
To view the document, visit: http://community.jboss.org/docs/DOC-15755
--------------------------------------------------------------
*+This document is a work in progress and subject to change.+*
In order to build JBoss Tools in your workspace (or on your local machine, if not in Eclipse), you need to have its dependencies available. There are a number of ways to accomplish this, depending on your needs and how much manual effort you'd like to expend.
First, you'll need the JBoss Tools sources on disk. Fetch sources from trunk (or another branch) into ~/tru (or another location on disk).
svn co http://anonsvn.jboss.org/repos/jbosstools/trunk/ http://anonsvn.jboss.org/repos/jbosstools/trunk/ ~/tru
Next, you can either install the target platform update site into your Eclipse install, or simply let Tycho fetch all the dependencies into a local m2 cached repository.
*------------------------------*
*
*
*OPTION 1: Install Target Platform Update Site into Eclipse*
Point the latest Eclipse 3.6.x build at this update site (generated from this http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/e36... e361-wtp322.target file). Be sure to show uncategorized features, then install everything.
http://download.jboss.org/jbosstools/updates/target-platform/latest/ http://download.jboss.org/jbosstools/updates/target-platform/latest/
After restarting Eclipse, you should have all the dependencies installed to develop JBoss Tools; however, if you want to use this Eclipse as the target platform against which to build using Tycho, you need to also unzip the latest http://http//download.eclipse.org/eclipse/downloads/drops/R-3.6.1-2010090... deltapack (eg., eclipse-M20101020-0925-delta-pack.zip) into your Eclipse root folder. Once you've done that, you can use the following commands to tell Tycho to use that Eclipse instead of doing its own resolution.
a) Build parent + target platform poms (should only take a few mins; includes 18M of downloaded artifacts into your local Maven cache, eg., ~/.m2).
cd ~/tru/build; mvn3 clean install -f http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml parent/pom.xml
b) Build one or more components:
cd ~/tru/build; mvn3 clean install +-U -B -e -fae -Dmaven.test.skip+ *-Dtycho.targetPlatform=/path/to/your/eclipse*
*------------------------------*
*
*
*OPTION 2: Let Tycho Resolve Dependencies Into Local Cache
*
a) Build parent + target platform poms (should only take a few mins; includes 18M of downloaded artifacts into your local Maven cache, eg., ~/.m2).
cd ~/tru/build; mvn3 clean install -f http://anonsvn.jboss.org/repos/jbosstools/trunk/build/parent/pom.xml parent/pom.xml
b) Build one or more components (when done, ~/.m2 will be 1.1G in size):
cd ~/tru/build; mvn3 clean install +-U -B -e -fae -Dmaven.test.skip+ *-P \!helios,helios-remote-target*
The 'helios-remote-target' will fetch all dependencies from this update site:
http://download.jboss.org/jbosstools/updates/target-platform/latest/ http://download.jboss.org/jbosstools/updates/target-platform/latest/
If have a local repo already mirrored on disk (for example, you downloaded http://download.jboss.org/jbosstools/updates/target-platform/e361-wtp322.... this 692M zip and unpacked it somewhere, you can use the 'helios-local-target' profile, but *will have to edit the parent/pom.xml* to point to the correct path on disk, and rebuild it. (The default path is the one that Hudson uses.)
vi parent/pom.xml # search for 'helios-local-target'
mvn3 clean install -f parent/pom.xml
mvn3 clean install +-U -B -e -fae -Dmaven.test.skip+ *-P \!helios,helios-local-target*
This is how the Hudson builds run: compile the parent & target platform pom.xml files, then build the desired component(s).
If you have the entire JBoss Tools tree on disk, you can do multi-component builds rather than having to build the WHOLE JBoss Tools using the bootstrap profiles in build/pom.xml. For example, to build Seam:
cd ~/tru/build; mvn3 clean install -Pseam-bootstrap,\!helios,helios-remote-target -U -B -e -fae
*------------------------------*
For other ways to build, see http://community.jboss.org/docs/DOC-15513 http://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15755]
Create a new document in JBoss Tools Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 2 months