Re: [riena-dev] Updating the build.properties

[Christian Campo <christian.campo@xxxxxxxxxxxx>]

Hi Elias,

thanks for doing that work and I agree that this is the way to go. I  
also agree that schema should be in the bin.includes since they help  
others to write plugins. They shouldnt have to get the source code in  
order to do that........

@Stefan: I look at the build.properties of riena.core that is  
mentioned in the bug and I think it should be adressed by the changes  
that Elias did. We found out with our next milestone....

christian

Am 13.06.2008 um 08:47 schrieb Stefan Liebig:

> Elias,
>
> Does this solve https://bugs.eclipse.org/bugs/show_bug.cgi?id=236407 ?
>
> Stefan
>
> Volanakis, Elias wrote:
> > I've updated the build properties in many of our plug-ins. As you  
> > know,
> > this file controls which non-source files get packaged into the  
> > plugin's
> > jar during the automated build.
> > In order to have functional plugins after the build, here is a list  
> > of
> > things that should normally be included the build properties:
> > * plugin.xml
> > * about.html * META-INF directory
> > * OSGI-INF directory
> > * icons directory
> > * lib directory / referenced jars
> > * schema directory (not strictly necessary, but helpful IMHO)
> > * any other non-java content that should be in the plugin's jar, like
> > configuration files that are needed at runtime, etc.
> >
> >
> > Remember to update the build.properties file when adding
> > files/directories to the root directory of your project.
> >
> > Kind regards,
> > Elias.
> >
> > _______________________________________________
> > riena-dev mailing list
> > riena-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/riena-dev
>
> _______________________________________________
> riena-dev mailing list
> riena-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/riena-dev