[jbosstools-dev] Who uses .target file?
Max Rydahl Andersen
manderse at redhat.com
Thu Mar 15 06:55:59 EDT 2012
> +1 to keep .target files.
>
> That's what we use here in concord.
>
> We have Development Target Platform which includes SDK's that match
> Runtime Target Platform components.
Where is that and why haven't you shared that ? :)
> The flow is:
> 1. Download Eclipse SDK, install Subversion Integration (WTP XML
> editing, M2E and etc);
wouldn't that come down with the target file ?
> 2. Checkout Dev TP into workspace;
> 3. Run maven clean install;
> 4. Open .target file and click use it as Target Platform in upper right
> corner;
> 5. Checkout or import (it is up to developer which way to go) component
> plugins;;
> 6. Build, rebuild and run without worries that you missed dependencies;
Yes - now we are talking...when can I get to try ? :)
> 3. you have sources for debugging for every dependency
but this step requires "double" .target files since the feature/plugin ids for SDKs are different/additions, right ?
> Now I am thinking about replacing step 1 with maven, so maven would be
> single entry point to build Dev Environment and target platform, then
> developer should just start built development environment, import TP
> into workspace, set .target file as cirrent target platform, export
> sources and start working.
Yes please!
More information about the jbosstools-dev
mailing list