Hello Jochen,
most projects only have a default projects.
I think if you have some really special scenario you can decide to have a specializes profile for those cases.
Eg. if you have some modules, which are only successful in a special setup, eg depending if it’s a windows- or unix-build it’s a good habit to have specific profiles for that.
Regards Britta
From: skalli-dev-bounces@xxxxxxxxxxx [mailto:skalli-dev-bounces@xxxxxxxxxxx] On Behalf Of Jochen Hiller
Sent: Donnerstag, 12. Mai 2011 13:03
To: Skalli project developer mailing list
Subject: Re: [skalli-dev] maven build and different profiles ? should we change that?
Hi Britta,
your suggestion sounds reasonable.
Is there a standard way other Eclipse projects are using Maven modules?
Bye, Jochen
On Thu, May 12, 2011 at 11:47 AM, Varwig, Britta <britta.varwig@xxxxxxx> wrote:
Hello,
as Jochen raised the problem and I also fall in that problem,
I would like to ask the question, what was the reason to have at least 3 profiles:
1) default with:
<module>org.eclipse.skalli.target</module>
<module>org.eclipse.skalli.parent</module>
<module>org.eclipse.skalli.api.java</module>
<module>org.eclipse.skalli.api.rest</module>
<module>org.eclipse.skalli.log</module>
<module>org.eclipse.skalli.core</module>
<module>org.eclipse.skalli.model.core</module>
<module>org.eclipse.skalli.common</module>
<module>org.eclipse.skalli.commands</module>
<module>org.eclipse.skalli.model.ext.misc</module>
<module>org.eclipse.skalli.view</module>
<module>org.eclipse.skalli.view.ext</module>
<module>org.eclipse.skalli.view.ext.impl</module>
<module>org.eclipse.skalli.view.theme</module>
<module>org.eclipse.skalli.maven</module>
<module>org.eclipse.skalli.testutil</module>
2) qa with:
<module>org.eclipse.skalli.core.test</module>
<module>org.eclipse.skalli.model.core.test</module>
<module>org.eclipse.skalli.model.ext.misc.test</module>
<module>org.eclipse.skalli.view.test</module>
<module>org.eclipse.skalli.api.java.test</module>
<module>org.eclipse.skalli.api.rest.test</module>
<module>org.eclipse.skalli.common.test</module>
<module>org.eclipse.skalli.view.ext.impl.test</module>
<module>org.eclipse.skalli.maven.test</module>
3) site with:
<module>org.eclipse.skalli.feature</module>
<module>org.eclipse.skalli.eclipse.feature</module>
<module>org.eclipse.skalli.testing.feature</module>
<module>org.eclipse.skalli.site</module>
Only reason that comes into my mind:
Minimize build time
Are there others?
What do you think of my suggestion:
* Put in the default profile ALL Skalli moduls.
* if someone people still see a need for a fast bild we can add a "fastBuild" profile containing the current default modules.
What do you think?
Regards Britta
_______________________________________________
skalli-dev mailing list
skalli-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/skalli-dev
