Sometime back I had the exact question in my mind and QoS (what you
mentioned as administration) and security were the only ones I could
think of.
Thanks,
Sahoo
David Weintraub wrote:
No one has answered the basic question: Why two repositories?
I know the differences between a release and s
On Fri, Oct 23, 2009 at 9:03 PM, Jörg Schaible wrote:
> Hi Niall,
>
> Niall Pemberton wrote:
>
>> Merci Beaucoup - thats fixed it. Still not sure why it just started
>> happening though.
>
> It seems the version of the plugin is not locked:
We had it specified in the section, but not
- adding i
No one has answered the basic question: Why two repositories?
I know the differences between a release and snapshot. but that doesn't
explain why the releases and snapshots are in two separate repositories. Why
not keep both snapshots and releases in the same repository. We know
something is a sna
Perhaps you may be interested by this : http://www.si4g.fr/open4g/
Best Regards,
David Meunier.
Le 23 oct. 09 à 13:32, Manos Batsis a écrit :
Neil Chaudhuri wrote:
A colleague at work expressed an interest in doing a lot of Maven-
like things in the JavaScript realm. I did some research and
Hi Althen,
Yes, I'll need a Jira issue and that you attach every xml file you're
modifying, zipped to be sure that nothing is modified in their content while
transferring them.
Regards,
Hervé
Le mercredi 21 octobre 2009, Althen, Uli a écrit :
> Hi Herve,
>
> I managed to pass this issue by sp
I have a flat multi-module project as follows:
myapp-parent
--pom.xml
myapp-persistence
--pom.xml
myapp-services
--pom.xml
The parent module is simply inherited by the others, and services aggregates
persistence.
I am using SVN SCM and Maven Release Plugin 2.0-beta-9. My goal with each
release
MRELEASE-484 and 485 say that I was using 2.0-beta-10 when I gave up.
On Fri, Oct 23, 2009 at 10:10 PM, Matt Milliss wrote:
> I've been trying to solve this exact same problem, it looks like a bug in
> the release plugin, what version are you using.
>
>
> On 15/10/2009 7:40 AM, Allan Ditzel wrote
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.4
This new release brings compatibility for Java EE 6 and a few bug fixes.
http://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration:
org.apache.m
On Sat, Oct 24, 2009 at 1:58 AM, Vincent F wrote:
>
> OK, thanks everyone for these additional infos. I may stick with WTP
> organisation then (using /WebContent/ instead of /src/main/webapp/) just for
> convenience in Eclipse.
You should be able to use /src/main/webapp thats what the file
.setti