On 10/28/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
Hi,
> On 10/24/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
> > what is the benefit of having a parent pom? I would prefer keeping
> > poms self-contained, an empty parent seems useless at the moment (all
> > the values comes from the OSGI manifest).
On 10/24/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> I'm working on deploying parent and all plugins to central repository.
I still didn't get the reason why having that parent pom could be useful...
There are a lot of common things to all eclipse projects like license.
Having the license all over all projects is not easy fo fix,
change,... Same problem for all common info
I actually improved the make-artifacts mojo in order to being able to
deploy generated artifacts
cool, I like that
(we needed good metadata, so it's better to
only use maven for deploying eclipse plugins) and I temporarily
commented out the parent pom addition.
I am currently testing it and I wanted to avoid the need for a parent
pom in order to be able to deploy to a clean remote repo, where
everything is handled by this plugin.
Carlos, let me know if and why you think it's better to put the parent back
fabrizio
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
