[JBoss AS 7 Development] - Logging Id's
by Remy Maucherat
Remy Maucherat [https://community.jboss.org/people/rmaucher] modified the document:
"Logging Id's"
To view the document, visit: https://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| P | = | Merged, but not complete |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI
* |
|
| *10600 - 10699* | *Controller Client* | C |
| *10700 - 10799* | *CMP* |
|
| *10800 - 10899* | *Host Controller (domain packages)* | C |
| *10900 - 10999* | *Host Controller (host packages)* | C |
| *11000 - 11099* | *EE* | C |
| *11100 - 11199* | *Embedded* | C |
| *11200 - 11299* | *JAXRS* | C |
| *11300 - 11399* | *JMX* | C |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *12200 - 12299* | *Management Client Content* | C |
| *12300 - 12399* | *Platform MBeans* | C |
| *12400 - 12499* | *Threads* |
|
| *13100 - 13199* | *Security* | W |
| available block(s) |
|
|
| *14100 - 14399* | *Ejb3* | P |
| *14400 - 14499* | *AppClient* | C |
| *14500 - 14599* | *JDR* | C |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Deployment HTTP API* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
| *15400 - 15499* | *Mail* | C |
| *15500 - 15699* | *Web Services* | C |
| *15700 - 15999* | *Server* | I |
| *1**6000 - 16099* | *Weld* |
|
| *16100 - 16199* | *EE Deployment* | C |
| *16200 - 16299* | *Configadmin* | C |
| *16300 - 16399* | *Jacorb* | I |
| available block(s) |
|
|
| *17000 - 17099* | *POJO* | W |
|
| *JAXR* |
|
|
| *Remoting* |
|
|
| *SAR* |
|
| *18000 - 18399* | *Web* | I |
|
| *Xts* |
|
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 11 months
[PicketBox Development] - JBoss AS7: Configuring SSL on JBoss Web
by Anil Saldhana
Anil Saldhana [https://community.jboss.org/people/anil.saldhana] created the document:
"JBoss AS7: Configuring SSL on JBoss Web"
To view the document, visit: https://community.jboss.org/docs/DOC-17503
--------------------------------------------------------------
*Disclaimer: Article is still in progress and is not definitive.*
There are 3 sets of connectors that one can configure with JBossWeb.
* AJP Connectors
* HTTP/HTTPS Connectors
* Native Connectors
*AJP Connectors* are primarily used to service requests coming from a web server such as Apache Httpd with mod_jk, mod_cluster etc in between.
*HTTP/HTTPS Connectors* are the standard connectors that can service web requests directly.
*Native Connectors* use the APR subsystem and provide better performance.
In JBoss AS7, the web subsystem configuration is performed in the web module in standalone.xml or domain.xml
h3.
h3. Important Points to remember:
1. The intention of the JBossWeb developers has been to unify the SSL configuration for all the connectors via the <ssl/> subelement.
2. When the native modules exist in JBoss AS (in the +lib+ folder of JBOSS_HOME/modules/org/jboss/as/web/main), the Native Connector settings come into play.
jboss-as-7.1.0.Final-SNAPSHOT/modules/org/jboss/as/web/main$ ls
jasper-jdt-7.0.3.Final.jar jboss-as-web-7.1.0.Final-SNAPSHOT.jar jbossweb-7.0.8.Final.jar lib
jasper-jdt-7.0.3.Final.jar.index jboss-as-web-7.1.0.Final-SNAPSHOT.jar.index jbossweb-7.0.8.Final.jar.index module.xml
anil@localhost:~jboss-as-7.1.0.Final-SNAPSHOT/modules/org/jboss/as/web/main$ ls lib/
linux-i686 linux-x86_64 macosx-i686 macosx-x86_64 win-i686 win-x86_64
As you can see the native libraries for each os architecture is available here.
*+===> If you do not want the native connector settings kicking in, you should remove the lib directory and its contents. <====
+*
h3.
h3. Working With KeyStores
For SSL settings, we will need access to a keystore.
If there is Client Certificate based authentication, then we will need to have access to a trust store also.
h3.
h3. Preferred KeyStores
For Native Connector settings, use the OpenSSL generated certificates and Keys.
For the Https Connector settings, you can use the Java Keytool generated keystore.
OpenSSL Generated Key and Certificate
Three Steps are involved.
Step 1:
$ openssl genrsa -des3 -out newkey.pem 1024
Generating RSA private key, 1024 bit long modulus
...........................................++++++
.........++++++
e is 65537 (0x10001)
Enter pass phrase for newkey.pem:
Verifying - Enter pass phrase for newkey.pem:
I used a pass phrase of "mykey"
Step 2:
$ openssl req -new -key newkey.pem -out server.csr
Enter pass phrase for newkey.pem:
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [XX]:US
State or Province Name (full name) []:IL
Locality Name (eg, city) [Default City]:Chicago
Organization Name (eg, company) [Default Company Ltd]:RedHat
Organizational Unit Name (eg, section) []:JBoss
Common Name (eg, your name or your server's hostname) []:Anil
Email Address []:anil@apache.org
Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:mykey
An optional company name []:
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-17503]
Create a new document in PicketBox Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 11 months
[JBoss AS 7 Development] - Logging Id's
by Remy Maucherat
Remy Maucherat [https://community.jboss.org/people/rmaucher] modified the document:
"Logging Id's"
To view the document, visit: https://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| P | = | Merged, but not complete |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI
* |
|
| *10600 - 10699* | *Controller Client* | C |
| *10700 - 10799* | *CMP* |
|
| *10800 - 10899* | *Host Controller (domain packages)* | C |
| *10900 - 10999* | *Host Controller (host packages)* | C |
| *11000 - 11099* | *EE* | C |
| *11100 - 11199* | *Embedded* | C |
| *11200 - 11299* | *JAXRS* | C |
| *11300 - 11399* | *JMX* | C |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *12200 - 12299* | *Management Client Content* | C |
| *12300 - 12399* | *Platform MBeans* | C |
| *12400 - 12499* | *Threads* |
|
| *13100 - 13199* | *Security* | W |
| available block(s) |
|
|
| *14100 - 14399* | *Ejb3* | P |
| *14400 - 14499* | *AppClient* | C |
| *14500 - 14599* | *JDR* | C |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Deployment HTTP API* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
| *15400 - 15499* | *Mail* | C |
| *15500 - 15699* | *Web Services* | C |
| *15700 - 15999* | *Server* | I |
| *1**6000 - 16099* | *Weld* |
|
| *16100 - 16199* | *EE Deployment* | C |
| *16200 - 16299* | *Configadmin* | C |
| *16300 - 16399* | *Jacorb* | I |
| available block(s) |
|
|
| *17000 - 17099* | *POJO* | W |
|
| *JAXR* |
|
|
| *Remoting* |
|
|
| *SAR* |
|
| *18000 - 18199* | *Web* | I |
|
| *Xts* |
|
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 11 months
[JBoss AS 7 Development] - Logging Id's
by Brian Stansberry
Brian Stansberry [https://community.jboss.org/people/brian.stansberry] modified the document:
"Logging Id's"
To view the document, visit: https://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| P | = | Merged, but not complete |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI
* |
|
| *10600 - 10699* | *Controller Client* | C |
| *10700 - 10799* | *CMP* |
|
| *10800 - 10899* | *Host Controller (domain packages)* | C |
| *10900 - 10999* | *Host Controller (host packages)* | C |
| *11000 - 11099* | *EE* | C |
| *11100 - 11199* | *Embedded* | C |
| *11200 - 11299* | *JAXRS* | C |
| *11300 - 11399* | *JMX* | C |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *12200 - 12299* | *Management Client Content* | C |
| *12300 - 12399* | *Platform MBeans* | C |
| *12400 - 12499* | *Threads* |
|
| *13100 - 13199* | *Security* | W |
| available block |
|
|
| *14100 - 14399* | *Ejb3* | P |
| *14400 - 14499* | *AppClient* | C |
| *14500 - 14599* | *JDR* | C |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Deployment HTTP API* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
| *15400 - 15499* | *Mail* | C |
| *15500 - 15699* | *Web Services* | C |
| *15700 - 15999* | *Server* | W |
| *1**6000 - 16099* | *Weld* |
|
| *16100 - 16199* | *EE Deployment* | C |
| *16200 - 16299* | *Configadmin* | C |
| *16300 - 16399* | *Jacorb* | I |
|
| *JAXR* |
|
| *17000 - 17099* | *POJO* | W |
|
| *Remoting* |
|
|
| *SAR* |
|
|
| *Web* |
|
|
| *Xts* |
|
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 11 months
[JBoss Tools Development] - How to Build JBoss Tools with Maven 3
by Nick Boldt
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document:
"How to Build JBoss Tools with Maven 3"
To view the document, visit: https://community.jboss.org/docs/DOC-16604
--------------------------------------------------------------
+*This article is a replacement for its precursor, https://community.jboss.org/docs/DOC-15513 How to Build JBoss Tools 3.2 with Maven 3.*+
+*Note that this article only discusses building from trunk. If you need to build from a branch, or switch between branches and/or trunk, see* https://community.jboss.org/docs/DOC-17497 How to Build JBoss Tools With Maven3 - Working With Branches+.
h2. Prerequisites
1. Java 1.6 SDK
2. Maven 3
3. Ant 1.7.1 or later
4. About 6 GB of free disk space if you want to run all integration tests for (JBoss AS, Seam and Web Services Tools) - *requires VPN access*
5. subversion client 1.6.X (should work with lower version as well)
h2. Environment Setup
h3. Maven and Java
Make sure your maven 3 is available by default and Java 1.6 is used.
mvn -version
should print out something like
*Apache Maven 3.0.2* (r1056850; 2011-01-08 19:58:10-0500)
*Java version: 1.6.0_20*, vendor: Sun Microsystems Inc.
*Java home: /usr/java/jdk1.6.0_20/jre*
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32.23-170.fc12.i686", arch: "i386", family: "unix"
h2.
h2. Building Locally Via Commandline
To run a local build of JBoss Tools 3.3 against the new Eclipse 3.7-based Target Platform, I suggest a three-step approach:
a) build the parent & target platform poms (v0.0.2-SNAPSHOT) *[ONLY NEEDED WHEN THESE CHANGE]*
b) resolve the target platform to your local disk *[ONLY NEEDED WHEN THESE CHANGE]*
c) build against your local copy of the target platform [every time you change sources and want to rebuild]
Once (a) and (b) are done, you need only perform (c) iteratively until you're happy (that is, until everything compiles). This lets you test changes locally before committing back to SVN.
*(a) and (b) need only be done when the parent pom and Target Platform (TP) change.* Of course if we get these published to nexus then you may not need those first bootstrapping steps. Stay tuned - work in progress.
*a) build the parent & target platform poms (v0.0.3-SNAPSHOT)*
svn co http://svn.jboss.org/repos/jbosstools/trunk jbosstools
cd jbosstools/build/parent
mvn clean install
...
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s]
[INFO] JBoss Tools Parent ................................ SUCCESS [0.461s]
...
*NOTE: You need not fetch the entire JBoss Tools tree from SVN (or Git (http://divby0.blogspot.com/2011/01/howto-partially-clone-svn-repo-to-git....
*Instead, you can just fetch the build/ folder and one or more component folders, then as before,*
*build the parent pom. After that, go into the component folder and run maven there (#runmavenpercomponent).*
mkdir jbosstools
cd jbosstools
svn co http://svn.jboss.org/repos/jbosstools/trunk/build
svn co http://svn.jboss.org/repos/jbosstools/trunk/jmx
cd jbosstools/build/parent
mvn clean install
...
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Tools Target Platform Definition ............ SUCCESS [0.724s]
[INFO] JBoss Tools Parent ................................ SUCCESS [0.461s]
...
*b) resolve the target platform to your local disk*
There are two ways to do this:
i) Download and unpack the latest TP zip, *OR*
ii) Resolve the TP using Maven or Ant
+i) Download and unpack the latest TP zip+
You can either download the TP as a zip [5] and unpack it into some folder on your disk. For convenience, the easiest is to unzip into jbosstools/build/target-platform/REPO/, since that's where the Maven or Ant process will by default operate.
You can do that with any browser or on a command line with curl or similar:
curl -C - -O http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/<actual-filename>.target.zip
...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 606M 100 606M 0 0 164k 0 1:02:54 1:02:54 --:--:-- 172k
and then unzip it:
mkdir jbosstools/build/target-platform/REPO
unzip *.target.zip -d jbosstools/build/target-platform/REPO
[5] http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/ http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/*...
*OR*
*
*
+ii) Resolve the TP using Maven or Ant with wget+
*MAC USERS**:* +you may need to install wget. + +http://download.cnet.com/Wget/3000-18506_4-128268.html Download it here++, or http://www.asitis.org/installing-wget-for-mac-os-x build it here.
+
cd jbosstools/build/target-platform
mvn clean install -Pget.local.target
The get.local.target profile will resolve the target platform file, multiple.target, as a p2 repository on your local disk in ~/trunk/build/target-platform/REPO/. It may take a while, so you're better off from a speed point-of-view simply fetching the latest zip [5]. However, if you want to see what actually happens to create the TP (as done in Hudson) this is the approach to take.
Since the Maven profile is simply a wrapper call to Ant, you can also use Ant 1.7.1 or later directly:
cd jbosstools/build/target-platform
ant help # show usage instructions
*c) build against your local copy of the target platform*
*LINUX / MAC USERS*
cd build
mvn clean install -U -B -fae -e -P local.site -Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.all.log.txt
(tee is a program that pipes console output to BOTH console and a file so you can watch the build AND keep a log.)
*WINDOWS USERS*
cd c:\trunk\build
mvn3 clean install -U -B -fae -e -P local.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/
or
mvn3 clean install -U -B -fae -e -Plocal.site -Dlocal.site=file:///C:/trunk/build/target-platform/REPO/ > build.all.log.txt
If you downloaded the zip and unpacked is somewhere else, use -Dlocal.site=file:/.../ to point at that folder instead.
#
If you would rather build a single component (or even just a single plugin), go into that folder and run Maven there:
cd ~/trunk/jmx
mvn3 clean install -U -B -fae -e -P local.site -Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.jmx.log.txt
+-- OR, if you prefer to use the "bootstrap profiles", which will build a given component PLUS its upstream JBoss Tools dependencies from source: --+
cd ~/trunk/build
mvn3 clean install -U -B -fae -e -P local.site,jmx-bootstrap -Dlocal.site=file:/${HOME}/trunk/build/target-platform/REPO/ | tee build.jmx.log.txt
++
#
h2. Building Locally In Eclipse
First, you must have installed m2eclipse into your Eclipse (or JBDS). You can install the currently supported version from this update site:
http://download.jboss.org/jbosstools/updates/indigo/ http://download.jboss.org/jbosstools/updates/indigo/
Next, start up Eclipse or JBDS and do *File > Import* to import the project(s) you already checked out from SVN above into your workspace.
https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-24-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-2...
Browse to where you have the project(s) checked out, and select a folder to import pom projects. In this case, I'm importing the parent pom (which refers to the target platform pom). Optionally, you can add these new projects to a working set to collect them in your Package Explorer view.
https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-24-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-2...
Once the project(s) are imported, you'll want to build them. You can either do *CTRL-SHIFT-X,M (Run Maven Build),* or right-click the project and select *Run As > Maven Build*. The following screenshots show how to configure a build job.
First, on the *Main* tab, set a *Name*, *Goals*, *Profile*(s), and add a *Parameter*. Or, if you prefer, put everything in the *Goals* field for simplicity:
+clean install -U -B -fae -e -Plocal.site -Dlocal.site=file://home/nboldt/tmp/JBT_REPO_Indigo/+
Be sure to check *Resolve Workspace artifacts*, and, if you have a newer version of Maven installed, point your build at that *Maven Runtime* instead of the bundled one that ships with m2eclipse.
https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-24-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-2...
On the *JRE* tab, make sure you're using a 6.0 JDK.
https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-24-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-2...
On the *Refresh* tab, define which workspace resources you want to refresh when the build's done.
https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-24-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-2...
On the *Common* tab, you can store the output of the build in a log file in case it's particularly long and you need to refer back to it.
https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-24-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-2...
Click *Run* to run the build.
https://community.jboss.org/servlet/JiveServlet/showImage/102-16604-24-13... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-16604-2...
Now you can repeat the above step to build any other component or plugin or feature or update site from the JBoss Tools repo. Simply import the project(s) and build them as above.
h2. Tips and tricks for making BOTH PDE UI and headless Maven builds happy
It's fairly common to have plugins compiling in eclipse while tycho would not work. Basically you could say that tycho is far more picky compared to Eclipse PDE.
h3.
Check your build.properties
Check build.properties in your plugin. If it has warnings in Eclipse, you'll most likely end with tycho failing to compile your sources. You'll have to make sure that you correct all warnings.
Especially check your build.properties to have entries for *source..* and *output..*
*
*
source.. = src/
output.. = bin/
h2.
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-16604]
Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 11 months
[JBoss Tools Development] - How to Build JBoss Tools with Maven 3 - Working With Branches
by Nick Boldt
Nick Boldt [https://community.jboss.org/people/nickboldt] created the document:
"How to Build JBoss Tools with Maven 3 - Working With Branches"
To view the document, visit: https://community.jboss.org/docs/DOC-17497
--------------------------------------------------------------
The usual process for JBoss Tools development is to at some point in the cycle declare a code freeze, branch the code in trunk to a new branch, and begin building BOTH the stable branch and unstable trunk in parallel.
This allows stabilization of the code base for the upcoming milestone, candidate release, or GA, while in parallel allowing developers to continue working on new features in the trunk stream.
*HOWEVER*, this workflow introduces some workflow requirements when building JBoss Tools locally.
So, here are the rules to remember when switching between branches.
*1. Always rebuild the parent pom* for the branch in which you're working before then building a component, site, feature, or plugin in that branch. This will ensure that your component is built against the correct upstream binaries from the composite staging site defined in the parent pom, ie., http://download.jboss.org/jbosstools/builds/staging/_composite_/3.3.indigo/ http://download.jboss.org/jbosstools/builds/staging/_composite_/3.3.indigo/ or http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/ http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/
cd ~/jbosstools-some-branch/build/parent; mvn clean install
*2. If not building everything locally, switch ~/.m2 repos when switching branches*. Because Tycho will resolve dependencies against your local ~/.m2 repository as well as the upstream composite staging site defined in the JBoss Tools parent pom, and doesn't care if the latest version of org.jboss.common is from M5 or Beta1 (it only cares that the timestamp is more recent) it may pick the wrong stream's binary. So, to avoid this, you need to either rebuild the upstream component locally using the bootstrap profiles, or maintain two ~/.m2 folders and switch between them when switching branches.
+# build something in trunk+
cd ~/jbosstools-trunk/build/parent; mvn clean install
cd ~/jbosstools-trunk/path/to/component-site-feature-or-plugin-to-build; mvn clean install++
+# move trunk m2 repo and start a new one+
mv ~/.m2 ~/.m2-trunk
+# this will take a while to bootstrap as the ~/.m2 repo is initially empty+
cd ~/jbosstools-some-branch/build/parent; mvn clean install
cd ~/jbosstools-some-branch/path/to/component-site-feature-or-plugin-to-build; mvn clean install
+# switch from branch back to trunk repo+
mv ~/.m2 ~/.m2-branch; mv ~/.m2-trunk ~/.m2++
+# build something in trunk+
cd ~/jbosstools-trunk/build/parent; mvn clean install
cd ~/jbosstools-trunk/path/to/component-site-feature-or-plugin-to-build; mvn clean install
3. *If building everying locally, use bootstrap profiles to rebuild everything upstream too*. This will guarantee you've rebuilt upstream components locally from the correct branch. Bootstrap profiles are listed here: https://anonsvn.jboss.org/repos/jbosstools/trunk/build/pom.xml https://anonsvn.jboss.org/repos/jbosstools/trunk/build/pom.xml
Thus, instead of building just a component, site, feature, or plugin...
cd ~/jbosstools-some-branch/build/parent; mvn clean install
+# then one or more of these+
cd ~/jbosstools-some-branch/jmx; mvn clean install
cd ~/jbosstools-some-branch/jmx/site; mvn clean install
cd ~/jbosstools-some-branch/jmx/features/org.jboss.tools.jmx.feature; mvn clean install
cd ~/jbosstools-some-branch/jmx/plugins/org.jboss.tools.jmx.core; mvn clean install
you must build the whole stack, like this:
cd ~/jbosstools-some-branch/build/parent; mvn clean install
cd ~/jbosstools-some-branch/build; mvn clean install -P jmx-bootstrap
If you discover a bootstrap profile is missing, incorrect, or incomplete, feel free to fix it in SVN or https://issues.jboss.org/secure/CreateIssue.jspa?pid=10020&issuetype=1 open a JIRA and report the issue with as much detail as possible.
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-17497]
Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 11 months
