I wouldn't have normally chimed in here against Stephen (He knows what he is on
about) however...
IMHO Staging only works with very small teams with dedicated infrastructure (in
which case QC generally are ok with a rebuild!).
If you have larger teams and share infrastructure (repo manager, CI)
On 21 January 2014 09:41, James Nord (jnord) wrote:
> I wouldn't have normally chimed in here against Stephen (He knows what he
> is on about) however...
>
> IMHO Staging only works with very small teams with dedicated
> infrastructure (in which case QC generally are ok with a rebuild!).
> If you
> > Or to put a contrived (yet realistic) example on this - Consider a
> > shared library Y. You have no auto testing of it so its only tested
> > inside products (otherwise you know its good to go - and wouldn't
> > release RCs).
> > Library Y is in a stage at version 1.2.3 This library is picke
It sounded like a single reactor release of everything to me... in which
case staging is fine
On 21 January 2014 11:07, James Nord (jnord) wrote:
>
> > > Or to put a contrived (yet realistic) example on this - Consider a
> > > shared library Y. You have no auto testing of it so its only tested
Hello
We use this to prevent deploying ears/wars into our repo. Everything is
built but not everything gets deployed.
Newer versions of the deploy plugin allow you to skip deployment so within
a few specific poms you can add.
maven-deploy-plugin
2.8.
Hello,
In our multi-module project we have one module that is only used for
development in our IDE. Is there a way to configure this project so that it
is always excluded from package phase?
Thanks,
-Todd
Hi Todd,
> In our multi-module project we have one module that is only used for
> development in our IDE. Is there a way to configure this project so
> that it is always excluded from package phase?
With Eclipse, you can do something similar using profiles:
eclipse
m2
Hi thank you very much for your response.
Maybe I asked in a wrong way but I have everything made yet with maven. I
have all the poms that build my whole project. I would like to know If
making only some changes in my pom.xml that package a "ear" I could change
it into an osgi bundle. I don't want
> have all the poms that build my whole project. I would like to know If
> making only some changes in my pom.xml that package a "ear" I could change
> it into an osgi bundle. I don't want to change my architecture or design
This is not an unreasonable question, but you just might not get an
answe
Hi,
I would have a question to Maven and additional resources.
I have build a simple Maven project, afterwards I did mvn eclipse:eclipse
and than I imported it into Eclipse.
This all worked fine.
Afterwards I would like to extend the pom.xml (below) in order to have new
file structure which is in
Hi everyone,
I am currently working on a maven plugin and we made use of the interface
ArtifactMetadataSource, which is deprectaed by now. I was trying to find
whatelse we could use but unfortunatly without any success until now.
It would be nice if someone could help me.
Best regards!
--
Vie
Hi PollerJava,
> I would like this additional folder structure: src/main/generated in
> my Maven project and also in my Eclipse project.
I suggest using M2E rather than the eclipse:eclipse goal.
With a modern "Eclipse for Java Developers" IDE, Maven support is built in,
and you don't need "eclip
Hi lsommer,
> we made use of the interface ArtifactMetadataSource, which is
> deprectaed by now. I was trying to find whatelse we could use but
> unfortunatly without any success until now.
Unfortunately, I do not have an answer for you. But I will take the
opportunity to sympathize with you -- a
13 matches
Mail list logo
