On 10/24/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
I'm working on deploying parent and all plugins to central repository.
wow, that's great :) just a question/decision to take before going on, anyway: at the moment eclipse poms uses "eclipse-plugin" as packaging. I was thinking to convert them to standard "jar" packaging, after the latest changes to the eclipse plugin. The reason is that any standard jar could be an osgi bundle, simply adding an appropriate manifest. I guess that in future there will be more and more jars in the repo that could be used as bundles (although they use the standard jar packaging): for example spring 2.1 will surely have osgi manifests in the standard distribution. That's the reason (along with a problem/bug in the artifactHandler in how it detects the packaging) why I recently made the eclipse plugin able to detect which jar is an osgi bundle by simply looking at its manifest. The natural evolution for this approach would be deploying also the eclipse jars as standard "jar" artifacts. This is one of the reason why all these features in the maven eclipse plugin have never been released: I am actually actively working to the development of eclipse RCP applications and I am now deeply testing/using/enhancing the maven-eclipse-plugin support for eclipse plugins and osgi bundles in general... WDYT? If you want to deploy all the artifacts to the central repo the packaging decision has to be taken now... PS. and a reminder, probably you already know that: you know that metadata will be absolutely required for eclipse artifacts? Transitive dependencies, coming from the osgi manifest, are usually declared with a version range and dependency resolution will fail if metadata are not available fabrizio
On 10/24/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote: > Hi Carlos, > > On 10/24/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Author: carlos > > Date: Tue Oct 24 06:36:54 2006 > > New Revision: 467331 > > > > URL: http://svn.apache.org/viewvc?view=rev&rev=467331 > > Log: > Use smaller groups and a parent pom for eclipse projects > > 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). > > and what about the license that was added to the pom, now removed? Do > you plan to deplo y a parent pom for that? > > fabrizio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
